On 16/07/2015 16:27, Nick Coghlan wrote:
On 16 July 2015 at 20:35, Guido van Rossum <gu...@python.org> wrote:
In which version? I don't see that phrase in the 3.5 docs.
The equivalent note in 3.x is "Do not use stdout=PIPE or stderr=PIPE
with this function. The child process will block if it generates
enough output to a pipe to fill up the OS pipe buffer as the pipes are
not being read from."
I think Chris is right that it's a docs bug - the warning is
applicable to subprocess.call and subprocess.check_call (which use
Popen.wait), but not to subprocess.check_output (which uses
Popen.communicate).
Cool, if I get a chance, I'll try and work up a patch, but it's been so
long since I last did any core-dev work that I'd need to read up on what
current processes are.
cheers,
Chris
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
