➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author giampaolo.rodola
Recipients giampaolo.rodola, josiah.carlson, josiahcarlson
Date 2009-04-02.01:03:21
SpamBayes Score 8.388577e-05
Marked as misclassified No
Message-id <1238634207.37.0.10074614667.issue5661@psf.upfronthosting.co.za>
In-reply-to
Content 
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.
History
Date User Action Args
2009-04-02 01:03:27giampaolo.rodolasetrecipients: + giampaolo.rodola, josiahcarlson, josiah.carlson
2009-04-02 01:03:27giampaolo.rodolasetmessageid: <1238634207.37.0.10074614667.issue5661@psf.upfronthosting.co.za>
2009-04-02 01:03:24giampaolo.rodolalinkissue5661 messages
2009-04-02 01:03:22giampaolo.rodolacreate