#12995: "source" exception attribute no longer handled properly by debug
exception
handler
--------------------------------------+-------------------------------------
Reporter: Glenn | Owner: nobody
Status: new | Milestone:
Component: Template system | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Comment (by Glenn):
Storing source information in the exception is cleaner. It means that any
templating engine supporting the interface can supply source context to
any exception renderer supporting it, without the user code sitting
between the two needing to manually ferry the information across with a
hook. (Not to suggest that the interface should be made public as it is;
it should also allow getting template source for each stack frame.)
Another reason (the original reason I noticed this) is discussed in ticket
#11461. DebugNodeList shouldn't be destroying the original exception to
attach information; it should simply be attaching the data to the existing
exception. r12586 makes cleanly fixing that impossible.
--
Ticket URL: <http://code.djangoproject.com/ticket/12995#comment:8>
Django <http://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 post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
