mirror of https://github.com/python/cpython.git
[3.11] [doc] Make subprocess.wait documentation more precise (GH-98700) (#112154)
[doc] Make subprocess.wait documentation more precise (GH-98700)
[doc] Make subprocess.wait doc more precise
An active loop is only used when the `timeout` parameter is used on
POSIX.
When no timeout is used, the code calls `os.waitpid` internally (which puts
the process on a sleep status). On Windows, the internal Windows API
call accepts a timeout parameter, so that is delegated to the OS.
(cherry picked from commit 81ab0e8a4a
)
Co-authored-by: Luis Pedro Coelho <luis@luispedro.org>
This commit is contained in:
parent
4c45927c3f
commit
f35322502a
|
@ -793,9 +793,10 @@ Instances of the :class:`Popen` class have the following methods:
|
|||
|
||||
.. note::
|
||||
|
||||
The function is implemented using a busy loop (non-blocking call and
|
||||
short sleeps). Use the :mod:`asyncio` module for an asynchronous wait:
|
||||
see :class:`asyncio.create_subprocess_exec`.
|
||||
When the ``timeout`` parameter is not ``None``, then (on POSIX) the
|
||||
function is implemented using a busy loop (non-blocking call and short
|
||||
sleeps). Use the :mod:`asyncio` module for an asynchronous wait: see
|
||||
:class:`asyncio.create_subprocess_exec`.
|
||||
|
||||
.. versionchanged:: 3.3
|
||||
*timeout* was added.
|
||||
|
|
Loading…
Reference in New Issue