Message235316
I’m adding nonblock-none.patch, which changes all the simple buffered read methods to return None when there is no non-blocking data available. I’d be interested to see if other people thought this was a sensible change.
* Documented existing behaviour of C “io” module buffered read(), readinto/1() returning None
* io.BufferedIOBase.read() and io.FileIO.readall() doc strings already mention returning None
* Removed false claims of buffered reads returning short for interactive streams, sockets and pipes
* Fixed _pyio return values to match C “io” module returning None
* Fixed BufferedIOBase.readinto/1() implementation to handle read/1() returning None
* Changed buffered read1() and peek() to return None |
|
Date |
User |
Action |
Args |
2015-02-03 07:17:44 | martin.panter | set | recipients:
+ martin.panter, pitrou, benjamin.peterson, stutzbach, anacrolix, neologix, docs@python, python-dev, sbt, petri.lehtinen |
2015-02-03 07:17:43 | martin.panter | set | messageid: <1422947863.46.0.636744684309.issue13322@psf.upfronthosting.co.za> |
2015-02-03 07:17:43 | martin.panter | link | issue13322 messages |
2015-02-03 07:17:43 | martin.panter | create | |
|