Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 81ab0e8

Browse filesBrowse files
authored
[doc] Make subprocess.wait documentation more precise (#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.
1 parent 985679f commit 81ab0e8
Copy full SHA for 81ab0e8

File tree

Expand file treeCollapse file tree

1 file changed

+4
-3
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+4
-3
lines changed

‎Doc/library/subprocess.rst

Copy file name to clipboardExpand all lines: Doc/library/subprocess.rst
+4-3Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -791,9 +791,10 @@ Instances of the :class:`Popen` class have the following methods:
791791

792792
.. note::
793793

794-
The function is implemented using a busy loop (non-blocking call and
795-
short sleeps). Use the :mod:`asyncio` module for an asynchronous wait:
796-
see :class:`asyncio.create_subprocess_exec`.
794+
When the ``timeout`` parameter is not ``None``, then (on POSIX) the
795+
function is implemented using a busy loop (non-blocking call and short
796+
sleeps). Use the :mod:`asyncio` module for an asynchronous wait: see
797+
:class:`asyncio.create_subprocess_exec`.
797798

798799
.. versionchanged:: 3.3
799800
*timeout* was added.

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.