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 pitrou
Recipients Arfrever, flox, giampaolo.rodola, janssen, jcea, pitrou, vstinner
Date 2010-04-06.11:39:25
SpamBayes Score 7.892545e-06
Marked as misclassified No
Message-id <1270553968.02.0.913671675079.issue8108@psf.upfronthosting.co.za>
In-reply-to
Content
Here is a new patch. It doesn't change handle_error() but instead ignores abruptly closed sockets when doing the SSL shutdown.

The underlying problem seems to be an asyncore limitation: close() can be called after an error such as EPIPE or ECONNABORTED, but asyncore doesn't give us any way to know in advance.
History
Date User Action Args
2010-04-06 11:39:28pitrousetrecipients: + pitrou, jcea, janssen, vstinner, giampaolo.rodola, Arfrever, flox
2010-04-06 11:39:28pitrousetmessageid: <1270553968.02.0.913671675079.issue8108@psf.upfronthosting.co.za>
2010-04-06 11:39:26pitroulinkissue8108 messages
2010-04-06 11:39:26pitroucreate