#24119: Backend-agnostic tracebacks on template rendering errors
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: Template system | Version: master
Severity: Normal | Resolution:
Keywords: multiple-template- | Triage Stage: Accepted
engines |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by prestontimmons):
I've worked to address part of this issue in:
https://github.com/django/django/pull/4254
Instead of setting `django_template_source` on exceptions and then having
the debug view call `ExceptionReporter.get_template_exception_info()`, all
exception info is provided by the engine as `Exception.template_debug`.
Any other engine can now show the same type of rendering traceback by
supplying a `template_debug` attribute. This is a generic dictionary with
values like `line`, `source_lines`, `start`, `end`, etc.
The is a lot less obtrusive than the existing implementation. Django is
able to provide this information by catching errors in only two spots--one
for parsing and one for rendering.
--
Ticket URL: <https://code.djangoproject.com/ticket/24119#comment:2>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.8431101c9756930f99e917bf5b85e3b0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
