[Django] #25463: RFE: support chained exceptions in DEBUG traceback view under Python 3.5+

5 views
Skip to first unread message

Django

unread,
Sep 25, 2015, 2:21:53 AM9/25/15
to django-...@googlegroups.com
#25463: RFE: support chained exceptions in DEBUG traceback view under Python 3.5+
---------------------------------+-----------------
Reporter: ncoghlan | Owner:
Type: New feature | Status: new
Component: Error reporting | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 1
---------------------------------+-----------------
I'm currently attempting to debug what appears to be an error handling bug
in Django REST Framework: https://github.com/tomchristie/django-rest-
framework/issues/3446

However, the error I *really* want to be investigating is the original
one, rather than the secondary failure in the DRF exception handling.

Python 3 captures this information in the `__context__` (or `__cause__`)
attribute on the exception object, as described in
https://www.python.org/dev/peps/pep-3134/

It would be handy if the DEBUG view could be updated to display that
information when it was available (although I have no idea how difficult
such a change would be)

--
Ticket URL: <https://code.djangoproject.com/ticket/25463>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Sep 25, 2015, 7:09:51 AM9/25/15
to django-...@googlegroups.com
#25463: RFE: support chained exceptions in DEBUG traceback view under Python 3.5+
---------------------------------+--------------------------------------
Reporter: ncoghlan | Owner:
Type: New feature | Status: closed

Component: Error reporting | Version: 1.8
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 1
---------------------------------+--------------------------------------
Changes (by timgraham):

* status: new => closed
* needs_better_patch: => 0
* resolution: => duplicate
* needs_tests: => 0
* needs_docs: => 0


Comment:

I believe this is done in Django 1.9 (see #23643).

--
Ticket URL: <https://code.djangoproject.com/ticket/25463#comment:1>

Reply all
Reply to author
Forward
0 new messages