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 alex, christian.heimes, dstufft, giampaolo.rodola, h.venev, janssen, pitrou
Date 2014-08-23.00:32:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1408753940.99.0.971672379074.issue22252@psf.upfronthosting.co.za>
In-reply-to
Content
> ssl.SSLWantReadError and ssl.SSLWantWriteError should inherit io.BlockingIOError.
> Generic code that works with non-blocking sockets will stop working with SSLSockets.

I'll have to think about that, but in any case non-blocking SSL code needs to be subtler than normal non-blocking code, because of this:

> Does anybody have any idea if SSLSocket.read() will need to write to the underlying socket or SSLSocket.write() need to read from it? AFAIK they don't.

Yet the documentation clearly tells you they can:
https://docs.python.org/3/library/ssl.html#notes-on-non-blocking-sockets
History
Date User Action Args
2014-08-23 00:32:21pitrousetrecipients: + pitrou, janssen, giampaolo.rodola, christian.heimes, alex, dstufft, h.venev
2014-08-23 00:32:20pitrousetmessageid: <1408753940.99.0.971672379074.issue22252@psf.upfronthosting.co.za>
2014-08-23 00:32:20pitroulinkissue22252 messages
2014-08-23 00:32:20pitroucreate