Message215711
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. |
|
Date |
User |
Action |
Args |
2014-04-07 16:15:01 | akira | set | recipients:
+ 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:01 | akira | set | messageid: <1396887301.73.0.311454308693.issue1191964@psf.upfronthosting.co.za> |
2014-04-07 16:15:01 | akira | link | issue1191964 messages |
2014-04-07 16:15:01 | akira | create | |
|