RetroSearch Browse

Thu Jul 16 12:35:58 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-July/140767.html

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 <chris at simplistix.co.uk>
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. Use Popen with the communicate() method when you need
> a stderr pipe."
>
> Given that check_output's implementation uses communicate(), how could
> stderr=PIPE cause a deadlock in a way that wouldn't happen if you called
> Popen.communicate() yourself?
>
> cheers,
>
> Chris
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/guido%40python.org
>

-- 
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150716/225b645e/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-July/140767.html below:

[Python-Dev] documentation / implementation question for subprocess.check_output