Opened 10 years ago
Closed 10 years ago
#24120 closed Bug (fixed)
Backend-agnostic debug information on template loading failures
| Reported by: | Aymeric Augustin | Owned by: | nobody |
|---|---|---|---|
| Component: | Template system | Version: | dev |
| Severity: | Normal | Keywords: | multiple-template-engines |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Currently ExceptionReporter.get_traceback_data() contains a special case for exceptions raised when a template cannot be found.
It retries loading the template with each template loader to figure out which paths were tried. Since the multiple templates engines refactor, this still works, but only if there's only one Django templates engine configured.
This logic should be embedded in the template engine. Third-part engines should have access to similar functionality through a public API.
Some ideas were brought up in this django-developers discussion.
Change History (3)
comment:1 by , 10 years ago
| Has patch: | set |
|---|
comment:2 by , 10 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
comment:3 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
In adff499: