Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity

#7177: clarify the potential PIPE deadlock warnings

This commit is contained in:
Philip Jenvey 2009-12-03 02:25:54 +00:00
parent 30b3b35cba
commit 2627553afa
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Doc/library/subprocess.rst
View File

@ -166,9 +166,10 @@ This module also defines two shortcut functions:
.. warning::
Like :meth:`Popen.wait`, this will deadlock if the child process
generates enough output to a stdout or stderr pipe such that it blocks
waiting for the OS pipe buffer to accept more data.
Like :meth:`Popen.wait`, this will deadlock when using
``stdout=PIPE`` and/or ``stderr=PIPE`` and the child process
generates enough output to a pipe such that it blocks waiting
for the OS pipe buffer to accept more data.
.. function:: check_call(*popenargs, **kwargs)
@ -260,9 +261,10 @@ Instances of the :class:`Popen` class have the following methods:
.. warning::
This will deadlock if the child process generates enough output to a
stdout or stderr pipe such that it blocks waiting for the OS pipe buffer
to accept more data. Use :meth:`communicate` to avoid that.
This will deadlock when using ``stdout=PIPE`` and/or
``stderr=PIPE`` and the child process generates enough output to
a pipe such that it blocks waiting for the OS pipe buffer to
accept more data. Use :meth:`communicate` to avoid that.
.. method:: Popen.communicate(input=None)