akira added the comment: STINNER Victor <rep...@bugs.python.org> writes: > >> I have implemented and would continue to lean towards continuing to > hide BrokenPipeError on the additional API endpoints. > > FYI asyncio.Process.communicate() ignores BrokenPipeError and > ConnectionResetError, whereas asyncio.Process.stdin.drain() (coroutine > to wait until all bytes are written) raises a BrokenPipeError or > ConnectionResetError if the child process exited. I think subprocess > has the same design.
Do Popen.write_nonblocking() and Popen.read_nonblocking() methods belong to the second category? Should they raise BrokenPipeError? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1191964> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
