[New-bugs-announce] [issue5661] asyncore should catch EPIPE while sending() and receiving()
Giampaolo Rodola'
report at bugs.python.org
Thu Apr 2 03:03:27 CEST 2009
New submission from Giampaolo Rodola' <billiejoex at users.sourceforge.net>:
I received a report from a pyftpdlib user:
http://code.google.com/p/pyftpdlib/issues/detail?id=104
...complaining that an unhandled EPIPE error might be thrown by
asyncore.py on OS X in certain circumstances which are hardly reproducible.
By googling a little about it it seems that he's not the first one who
got this problem:
http://mail.python.org/pipermail/medusa-dev/2003/000852.html
https://bugs.launchpad.net/zope2/+bug/142654
I think it makes sense modifying dispatcher.send() and dispatcher.recv()
to include EPIPE as error condition to indicate that the connection has
been closed and call handle_close() as consequence.
The patch in attachment does that.
----------
components: Library (Lib)
files: asyncore.patch
keywords: patch
messages: 85125
nosy: giampaolo.rodola, josiah.carlson, josiahcarlson
severity: normal
status: open
title: asyncore should catch EPIPE while sending() and receiving()
type: behavior
versions: Python 2.6, Python 2.7, Python 3.0, Python 3.1
Added file: http://bugs.python.org/file13566/asyncore.patch
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5661>
_______________________________________
More information about the New-bugs-announce
mailing list