[docs] [issue13322] buffered read() and write() does not raise BlockingIOError

[Martin Panter]

Martin Panter added the comment:

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

----------
Added file: http://bugs.python.org/file37995/nonblock-none.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13322>
_______________________________________