Agreed with Colleen here in comment #14, we can close it as "won't fix" due to the same reasons as the bug linked, plus the fact that this does not appear to be an issue with the migration to Flask in Stein.
Agreed with Colleen here in comment #14, we can close it as "won't fix" due to the same reasons as the bug linked, plus the fact that this does not appear to be an issue with the migration to Flask in Stein.