Skip to content

gh-138234: clarify returncode behavior for subprocess_exec vs subprocess_shell #138536

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+10 −2
Open

gh-138234: clarify returncode behavior for subprocess_exec vs subprocess_shell #138536

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions Doc/library/asyncio-subprocess.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -305,8 +305,16 @@ their completion.

A ``None`` value indicates that the process has not terminated yet.

A negative value ``-N`` indicates that the child was terminated
by signal ``N`` (POSIX only).
For processes created with :func:`~asyncio.create_subprocess_exec`, a negative
value ``-N`` indicates that the child was terminated by signal ``N``
(POSIX only).

For processes created with :func:`~asyncio.create_subprocess_shell`, the
return code reflects the exit status of the shell itself (e.g. ``/bin/sh``),
which may map signals to codes such as ``128+N``. See the
documentation of the shell (for example, the Bash manual's Exit Status)
for details.



.. _asyncio-subprocess-threads:
Expand Down
Loading