#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: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------------
Comment (by jamesh):
For what it is worth, I haven't noticed any problems using the patch I
attached to the bug report (both for normal Django error pages and the
developer debug error page).
The wsgiref module ignores the exc_info argument provided that the
response headers haven't been sent (not a problem for Django, since it
only calls start_response once).
The same seems to be true for mod_wsgi:
http://code.google.com/p/modwsgi/source/browse/mod_wsgi/mod_wsgi.c#2600
And similar for Paste:
https://bitbucket.org/ianb/paste/src/852439f67241/paste/httpserver.py#cl-153
https://bitbucket.org/ianb/paste/src/852439f67241/paste/modpython.py#cl-176
And Twisted:
http://twistedmatrix.com/trac/browser/trunk/twisted/web/wsgi.py#L256
--
Ticket URL: <https://code.djangoproject.com/ticket/16674#comment:9>
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.
