[issue35182] Popen.communicate() breaks when child closes its side of pipe but not exits

Change by Andriy Maletsky : -- pull_requests: +16540 pull_request: https://github.com/python/cpython/pull/17023 ___ Python tracker <https://bugs.python.org/issue35

[issue35182] Popen.communicate() breaks when child closes its side of pipe but not exits

Change by Andriy Maletsky : -- keywords: +patch pull_requests: +16538 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/17020 ___ Python tracker <https://bugs.python.org/issu

[issue35182] Popen.communicate() breaks when child closes its side of pipe but not exits

Andriy Maletsky added the comment: @josh.r but you’re correct regarding cached data that isn’t sent on subsequent communicate() calls. If the child consumes the input too slowly, and timeout occurs before sending all input, the remaining part will be lost. Maybe it is not a bug, but it’s

[issue36434] Zipfile breaks if signalled during write()

New submission from Andriy Maletsky : Consider a simple write to a zip file: import zipfile with zipfile.ZipFile('/workdir/archive.zip', 'w', compression=zipfile.ZIP_DEFLATED) as zip_archive: zip_archive.write('/workdir/data.csv', arcname='data.cs

[issue35182] Popen.communicate() breaks when child closes its side of pipe but not exits

Change by Andriy Maletsky : -- components: +Library (Lib) ___ Python tracker <https://bugs.python.org/issue35182> ___ ___ Python-bugs-list mailing list Unsub

[issue35182] Popen.communicate() breaks when child closes its side of pipe but not exits

Change by Andriy Maletsky : -- type: crash -> behavior ___ Python tracker <https://bugs.python.org/issue35182> ___ ___ Python-bugs-list mailing list Unsubscrib

[issue35182] Popen.communicate() breaks when child closes its side of pipe but not exits

New submission from Andriy Maletsky : When communicate() is called in a loop, it crashes when the child process has already closed any piped standard stream, but still continues to be running. How this happens: 1) the parent waits for the child events inside communicate() call 2) the child

[issue32102] Add "capture_output=True" option to subprocess.run

Change by Andriy Maletsky : -- pull_requests: +8204 ___ Python tracker <https://bugs.python.org/issue32102> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34074] Asyncio breaks coroutine finalization process

Andriy Maletsky added the comment: I meant that my example is a complete python script, and after `loop.run_forever()` the interpreter stops. So I expected every python object to be destructed on interpreter shutdown, but coro's `close()` is not called. To make example more practical,

[issue34074] Asyncio breaks coroutine finalization process

New submission from Andriy Maletsky : Source: https://stackoverflow.com/q/51245011/6275324 Asyncio somehow breaks coroutine finalization. I believe there may be a bug in C implementation (_asyncio) of tasks or futures. Reproducible within version 3.7.0@python:3.7 docker container. Consider