#27175: Deprecate silencing exceptions raised while rendering the {% include %}
template tag
------------------------------------------------+------------------------
Reporter: jdufresne | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Template system | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
Django developers discussion https://groups.google.com/d/topic/django-
developers/hscW1VboJxY
As proposed and supported in the linked discussion, deprecate the
silencing of exceptions while rending the `{% include %}` template tag.
As this silencing behavior only occurs when `template.debug=True`, it is
difficult to rely on this as a "feature". Further, the behavior could
silence actual bugs during development as well as lead to a different
error reporting path when used in production. (e.g. Errors are reported
through Django template logging instead of through Sentry.)
--
Ticket URL: <https://code.djangoproject.com/ticket/27175>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.ac9e89ccdeb0dfae9e8a04953be0a038%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
