[issue23242] asyncio: Process must close the transport when the process exit

2017-01-07 Thread Alex Grönholm
Alex Grönholm added the comment: Are you sure this has been fixed? The attached script reproduces the bug 100% reliably on my laptop. -- Added file: http://bugs.python.org/file46198/read_subprocess.py ___ Python tracker

[issue23242] asyncio: Process must close the transport when the process exit

2017-01-07 Thread Alex Grönholm
Changes by Alex Grönholm : -- nosy: +alex.gronholm versions: +Python 3.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue23242] asyncio: Process must close the transport when the process exit

2015-01-15 Thread STINNER Victor
STINNER Victor added the comment: > I'm not sure that it's the most efficient way to close the transport. It may > be better to close the transport in the connection_lost() method of the > protocol. "process_exited", not "connection_lost". I implemented this option which is simpler and more e

[issue23242] asyncio: Process must close the transport when the process exit

2015-01-15 Thread Roundup Robot
Roundup Robot added the comment: New changeset df493e9c6821 by Victor Stinner in branch '3.4': Issue #23242: asyncio.SubprocessStreamProtocol now closes the subprocess https://hg.python.org/cpython/rev/df493e9c6821 -- nosy: +python-dev ___ Python trac

[issue23242] asyncio: Process must close the transport when the process exit

2015-01-14 Thread STINNER Victor
New submission from STINNER Victor: The asyncio.subprocess.Process class never closes the subprocess transport, whereas this transport is private. I propose to close the transport as soon as possible: when transport.get_returncode() is called and its result is not None. I'm not sure that it's