#4444: broken pipe issue
-------------------------------------+-------------------------------------
Reporter: vanderkerkoff | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version: master
Component: django-admin.py | Resolution: fixed
runserver | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: broken pipe 32 | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"9253042d53d61b23b3f727a00c41e8089be73836"]:
{{{
#!CommitTicketReference repository=""
revision="9253042d53d61b23b3f727a00c41e8089be73836"
Fixed #4444 - Made runserver suppress 'broken pipe' errors
One handler in WSGIServer, to catch the error when raised from
SocketServer.BaseServer's finish_request, and one in WSGIRequestHandler
(by creating a subclass of ServerHandler), to catch the error when
raised in wsgiref.handlers.BaseHandler's finish_response.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/4444#comment:30>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.01ed7af078c68c0e34b59f60f6431846%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
