#16674: Django's WSGI Handler should report exceptions to the start_response()
callback
-----------------------------------------+------------------------------
Reporter: jamesh | Owner: nobody
Type: Uncategorized | Status: new
Milestone: | Component: Core (Other)
Version: SVN | Severity: Normal
Resolution: | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------------
Changes (by jamesh):
* has_patch: 0 => 1
Comment:
I've attached a patch that offers a sample implementation of what I'm
after. With this patch, I was able to capture error reports at the WSGI
level with both the DEBUG=True error page and with custom handler500 error
pages.
I'm not particularly happy with the way I'm capturing the exception
context in the handle_uncaught_exception() method. Perhaps temporarily
storing the context on the request object would be a cleaner way of
passing it up to __call__() compared to using thread local storage.
WSGIHandler is using its own request class after all.
--
Ticket URL: <https://code.djangoproject.com/ticket/16674#comment:5>
Django <https://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.
