On Saturday 25 February 2017 16:28:17 Tim Graham wrote: > My proposal was only for the use of undefined variables in template > tags. I didn't realize that the behavior of undefined variables in > some tags resolving to None is documented, but I still think it's a > useful change to raise an exception instead. The philosophy that > template tags shouldn't raise exceptions is more unhelpful than > helpful in my experience.
I sincerely hope that the change only affects DEBUG mode (including the include change). But once the templates are validated and working as they should, they should not generate exceptions unless Django provides a way to catch them. For example, if a service is unavailable that makes up a small part of a page, I do not want the whole page to crash or information to leak. -- Melvyn Sopacua -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/2409576.D1JWrnJBHJ%40devstation. For more options, visit https://groups.google.com/d/optout.
