Opened 16 years ago
Closed 16 years ago
#12294 closed (duplicate)
Exception info caught in django/template/debug.py should be propagated
| Reported by: | kuon | Owned by: | nobody | 
|---|---|---|---|
| Component: | Template system | Version: | 1.1 | 
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no | 
| Needs tests: | no | Patch needs improvement: | no | 
| Easy pickings: | no | UI/UX: | no | 
Description
In django/template/debug.py at line 76, the exception is caught and replaced by another one, but info from the original exception are missing on the debug output.
For example, I was working with django-cms, installed a plugin, and that plugin was raising an exception. That exception was caught and replaced by a TemplateSyntaxError (line 78) with my own template name.
Original exception should be visible somewhere in the final debug output.
  Note:
 See   TracTickets
 for help on using tickets.
    
Are you using Python 2.6? That is the only time I have seen the original exception information get completely lost, previously its traceback was included in the exception value for the TemplateSyntaxError.
#11461 has a couple of different alternative patches for this.