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 shevek
Recipients animus, christian.heimes, docs@python, noxxi, pitrou, shevek
Date 2014-05-17.19:39:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1400355541.0.0.515464542416.issue21430@psf.upfronthosting.co.za>
In-reply-to
Content
After trying to use this, I think ssl.pending is a valuable function that should be supported and documented.

My use case is a half-synchronous system, where I want most calls to block but asynchronous events are possible as well.  Switching the socket between blocking and non-blocking all the time is annoying and results in code that is harder to read.

With ssl.pending, I can simply repeat the read as long as data is pending.  Setting my buffer size high might technically work, but that seems too fragile.  I don't like using an undocumented function either, but I'm hoping that gets fixed. ;-)
History
Date User Action Args
2014-05-17 19:39:01sheveksetrecipients: + shevek, pitrou, christian.heimes, docs@python, animus, noxxi
2014-05-17 19:39:01sheveksetmessageid: <1400355541.0.0.515464542416.issue21430@psf.upfronthosting.co.za>
2014-05-17 19:39:00sheveklinkissue21430 messages
2014-05-17 19:39:00shevekcreate