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 Arfrever, flox, giampaolo.rodola, janssen, pitrou, vstinner
Date 2010-03-14.19:44:48
SpamBayes Score 0.00022406498
Marked as misclassified No
Message-id <1268595890.37.0.596719187423.issue8108@psf.upfronthosting.co.za>
In-reply-to
Content
> AFAICT, his proposed "quick fix" snippet should be good enough for us.

Depends on what we want.  It just suppresses information that's now available.  What we'd really like is for the caller to recognize that close() can fail, and should be re-tried if it does.  That requires that we signal the error back up and out of the ssl module.  It seems to me that any non-blocking code should recognize this and respect it.

Again, why does this failure only show up in the FTP test?  Why aren't we seeing it elsewhere?
History
Date User Action Args
2010-03-14 19:44:50janssensetrecipients: + janssen, pitrou, vstinner, giampaolo.rodola, Arfrever, flox
2010-03-14 19:44:50janssensetmessageid: <1268595890.37.0.596719187423.issue8108@psf.upfronthosting.co.za>
2010-03-14 19:44:49janssenlinkissue8108 messages
2010-03-14 19:44:48janssencreate