Message277517
Hi,
Currently, subprocess.Popen performs blocking IO in its constructor (at least on Unix): it reads on a pipe in order to detect outcome of the pre-exec and exec phase in the new child. There is no way yet to modify this behavior as this blocking call is part of a long Popen._execute_child() method.
This is a problem in asyncio (asyncio.subprocess_exec and asyncio.subprocess_shell).
I would like to submit a patch which breaks Popen.__init__() and Popen._execute_child() in several methods so it becomes possible to avoid blocking calls (read on pipe and waitpid) by overriding a few private methods without duplicating too much code. The goal is to use it in asyncio, as described in this pull request (which currently monkey-patches Popen):
https://github.com/python/asyncio/pull/428
This patch only targets the unix implementation.
Thanks for your feedback. |
|
Date |
User |
Action |
Args |
2016-09-27 14:26:43 | martius | set | recipients:
+ martius |
2016-09-27 14:26:43 | martius | set | messageid: <1474986403.83.0.165864194914.issue28287@psf.upfronthosting.co.za> |
2016-09-27 14:26:43 | martius | link | issue28287 messages |
2016-09-27 14:26:43 | martius | create | |
|