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 janssen
Recipients flox, giampaolo.rodola, janssen, pitrou, vstinner
Date 2010-03-12.20:18:01
SpamBayes Score 0.00025262602
Marked as misclassified No
Message-id <1268425083.1.0.160571267021.issue8108@psf.upfronthosting.co.za>
In-reply-to
Content
I think Giampaolo is right about this not being an ssl.py issue.  Could the exception handling in ftp.py perhaps also be made more sophisticated?  I'd really love to understand what the state of the TCP connection is here.  I'm presuming that it's still open, because otherwise you'd get a different error from OpenSSL.  So what's the error that's triggering this call?  Is it simply that the sender has run out of stuff to send?

Also, I think that asyncore.py is stingy about what information it sends.  At the very least, it could invoke handle_error() with the exception it's handling as an argument.
History
Date User Action Args
2010-03-12 20:18:03janssensetrecipients: + janssen, pitrou, vstinner, giampaolo.rodola, flox
2010-03-12 20:18:03janssensetmessageid: <1268425083.1.0.160571267021.issue8108@psf.upfronthosting.co.za>
2010-03-12 20:18:01janssenlinkissue8108 messages
2010-03-12 20:18:01janssencreate