Martin Panter <vadmium...@gmail.com> added the comment: The general problem of non-blocking reads with BufferedIOBase is covered by Issue 13322. The documentation and implementations do not agree. I suggest to not rely on any particular behaviour reading BufferedIOBase objects in non-blocking mode.
The problem of the concrete class BufferedReader (what “stdin.buffer” usually is) was also recently raised in Issue 35869. ---------- nosy: +martin.panter resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> buffered read() and write() does not raise BlockingIOError _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue36294> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
