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 akira
Recipients Andrew.Boettcher, ajaksu2, akira, astrand, cvrebert, ericpruitt, eryksun, giampaolo.rodola, janzert, josiahcarlson, ooooooooo, parameter, r.david.murray, rosslagerwall, sbt, techtonik, v+python
Date 2014-04-07.16:15:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1396887301.73.0.311454308693.issue1191964@psf.upfronthosting.co.za>
In-reply-to
Content
Could `read_nonblocking()`, `write_nonblocking()` raise OSError(EAGAIN) (it could be named `ResourceTemporarilyUnavailableError`) if read/write would block?

It would allow to distinguish EOF (permanent condition) from "read/write would block" (temporarily condition) without additional API calls.
History
Date User Action Args
2014-04-07 16:15:01akirasetrecipients: + akira, josiahcarlson, astrand, parameter, techtonik, giampaolo.rodola, ajaksu2, ooooooooo, v+python, r.david.murray, cvrebert, ericpruitt, Andrew.Boettcher, rosslagerwall, sbt, janzert, eryksun
2014-04-07 16:15:01akirasetmessageid: <1396887301.73.0.311454308693.issue1191964@psf.upfronthosting.co.za>
2014-04-07 16:15:01akiralinkissue1191964 messages
2014-04-07 16:15:01akiracreate