On 16/07/2015 16:27, Nick Coghlan wrote:
On 16 July 2015 at 20:35, Guido van Rossum 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 out
On 16 July 2015 at 20:35, Guido van Rossum 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 buffe
In which version? I don't see that phrase in the 3.5 docs.
On Thu, Jul 16, 2015 at 9:52 AM, Chris Withers
wrote:
> Hi All,
>
> Curious to see this in the docs for subprocess.check_output: "Do not use
> stderr=PIPE with this function as that can deadlock based on the child
> process error volume.
Hi All,
Curious to see this in the docs for subprocess.check_output: "Do not use
stderr=PIPE with this function as that can deadlock based on the child
process error volume. Use Popen with the communicate() method when you
need a stderr pipe."
Given that check_output's implementation uses co
