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 amaury.forgeotdarc, barry, ddvoinikov, exarkun, flox, giampaolo.rodola, janssen, jimsmyth, josiah.carlson, josiahcarlson, pitrou, qwavel, rhettinger, srid
Date 2010-03-22.08:22:38
SpamBayes Score 0.0008166177
Marked as misclassified No
Message-id <1269246161.4.0.299316773044.issue3890@psf.upfronthosting.co.za>
In-reply-to
Content
> The intuitive explanation seems to be:
> - there are some bytes available for reading on the *TCP socket*, 
> therefore asyncore calls the read handler
> - however, there are not enough bytes for OpenSSL to actually decrypt 
> any data, which is why we get SSL_ERROR_WANT_READ when trying to read 
> from the *SSL socket*
> The following patch seems to fix test_ftplib; any thoughts?

The patch seems ok to me. This is how it was supposed to be in the first place if ssl.py behaved as expected with non blocking sockets.
History
Date User Action Args
2010-03-22 08:22:41giampaolo.rodolasetrecipients: + giampaolo.rodola, barry, rhettinger, josiahcarlson, exarkun, amaury.forgeotdarc, janssen, pitrou, josiah.carlson, ddvoinikov, srid, flox, qwavel, jimsmyth
2010-03-22 08:22:41giampaolo.rodolasetmessageid: <1269246161.4.0.299316773044.issue3890@psf.upfronthosting.co.za>
2010-03-22 08:22:39giampaolo.rodolalinkissue3890 messages
2010-03-22 08:22:38giampaolo.rodolacreate