Created on 2016-04-26 04:40 by oconnor663, last changed 2016-05-14 01:42 by berker.peksag. This issue is now closed.
Setting stdin=PIPE and then calling communicate(b"") should close the child's stdin immediately, similar to stdin=DEVNULL. Instead, communicate() treats b"" like None and leaves the child's stdin open, which makes the child hang forever if it tries to read anything. I have a PR open with a fix and a test: https://github.com/python/cpython/pull/33
python/cpython is a semi-official read-only mirror of hg.python.org/cpython. We haven't switched to GitHub yet. You may want to open a pull request to https://github.com/python/asyncio See https://github.com/python/asyncio/wiki/Contributing for details.
Thanks for the heads up, Berker, I've re-submitted the PR as https://github.com/python/asyncio/pull/335.
Related: The asyncio communicate() method differs from standard subprocess in how it treats input bytes when stdin is (probably mistakenly) not set to PIPE. Like this:
proc = await create_subprocess_shell("sleep 5")
await proc.communicate(b"foo") # Oops, I forgot stdin=PIPE above!
The standard, non-async version of this example, communicate would ignore the input bytes entirely. But here in the asyncio version, communicate will try to write those bytes to stdin, which is None, and the result is an AttributeError.
Since the user probably only hits this case by mistake, I think raising an exception is preferable. But it would be nice to raise an exception that explicitly said "you've forgotten stdin=PIPE" instead of the unhelpful "'NoneType' object has no attribute 'write'". Maybe it would be worth cleaning this up while we're here?
New changeset 148757a88f19 by Yury Selivanov in branch '3.5': Issue #26848: Fix asyncio/subprocess.communicate() to handle empty input. https://hg.python.org/cpython/rev/148757a88f19 New changeset f5e69e2f50d7 by Yury Selivanov in branch 'default': Merge 3.5 (issue #26848) https://hg.python.org/cpython/rev/f5e69e2f50d7