I may be way off base here, but I actually feel like string_if_invalid should eventually be removed. It seems like a really bad idea to have a setting that can muck up an application in unexpected ways. Meanwhile, settings like DEBUG=True can't muck up your application, even if they're not secure to leave on in production.</digression>
I think the answer to whether it should be treated as a regression is the inverse of whether there are other places where template logic could unexpectedly change based on this setting. Fixing this one situation by checking for a specific error seems wrong, unless it's the only such case that could be reasonably expected to cause this problem. Based on the warning in the docs (about the admin), I take it that is not the case. So without further ado, I vote "not a regression". -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/4431f173-db1f-4b5d-9941-1ca1fb4697e0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
