On Jan 14, 2016 7:50 AM, "guettli" <guettl...@thomas-guettler.de> wrote: > > I would like to do this: > > turn on "string_if_invalid" as a ‘development default’ > > The django docs say: > > While string_if_invalid can be a useful debugging tool, it is a bad idea to turn it on as a ‘development default’. > > https://docs.djangoproject.com/en/1.9/ref/templates/api/#how-invalid-variables-are-handled > > We were hit by some nasty bugs in production environment which were not detected in our continous integration plattform. > > If "string_if_invalid" (or former TEMPLATE_STRING_IF_INVALID) would have been activated, > we would have noticed the bug, and the broken code would have gone live. > > How do you handle this? >
Why not have a second batch of tests that use a settings.py file with a non default value for "string_if_invalid" that runs if the default settings file passes? I've never dealt with a CI platform, but I'm assuming you can do something like that. - James -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2Be%2BciXRm4rdwB-icDSsNFwqAhk-qYes9DieOKQXK%3D8mPVCGmQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
