#24119: Backend-agnostic tracebacks on template rendering errors -------------------------------------+------------------------------------- Reporter: aaugustin | Owner: nobody Type: Bug | Status: new Component: Template | Version: master system | Keywords: multiple-template- Severity: Normal | engines Triage Stage: Accepted | Has patch: 0 Needs documentation: 0 | Needs tests: 0 Patch needs improvement: 0 | Easy pickings: 0 UI/UX: 0 | -------------------------------------+------------------------------------- Currently `ExceptionReporter.get_traceback_data()` contains a special case for exceptions raised during template rendering.
If the exception has a `django_template_source` attribute, which is set by the `Debug` variants of the Django template language's classes, information is gathered by `ExceptionReporter.get_template_exception_info()` This logic should be embedded in the template engine. Third-part engines should have access to similar functionality through a public API. -- Ticket URL: <https://code.djangoproject.com/ticket/24119> 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.54c35a580e80f865471294c965c4347b%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.