#11368: debug error reporter should include traceback for nested exceptions
-------------------------------------+--------------------------------------
Reporter: jfire | Owner: nobody
Status: new | Milestone:
Component: Core framework | Version: 1.0
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by Glenn):
* cc: [email protected] (added)
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
This isn't the right fix. This would have to be implemented in every
custom exception reporter, including third-party ones that don't know
about Django exceptions at all.
The actual problem is that DebugNodeList is raising the new exception
incorrectly. It needs to include the original traceback.
{{{
try:
...
catch Exception, e:
raise NewException, None, sys.exc_info()[2]
}}}
See #11461.
--
Ticket URL: <http://code.djangoproject.com/ticket/11368#comment:1>
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
