> Has anyone relied on the exception silencing behavior as a "feature" when
using {% include %}?Not here. +1 on deprecating the silencing behavior. I have created a ticket [0] and PR [1] so others may get a sense of the bigger picture change and how it could affect Django. Feedback welcome. More generally, I find the template engine's behavior of replacing exceptions with an empty string to cause more bugs than it prevents. In my experience, loud errors will more likely be caught during development, unit tests, and manual testing. [0] https://code.djangoproject.com/ticket/27175 [1] https://github.com/django/django/pull/7208 -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/CADhq2b7%3Daxpcduaas68ihWugLhiffTPmAx0bQoyTy%3Dsa8Sq7GA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
