From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Tue, 7 Sep 2021 18:43:42 +0000 (-0700)
Subject: bpo-24888: Clarify subprocess.check_call propagates exceptions if unable to start... 
X-Git-Tag: v3.9.8~184
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=2363910662cda4dcf574da68b4633b55e5fc0f9c;p=thirdparty%2FPython%2Fcpython.git

bpo-24888: Clarify subprocess.check_call propagates exceptions if unable to start process (GH-28018) (GH-28223)

(cherry picked from commit 19a304ba990481f0381a5316096b6b3cf2dff381)

Co-authored-by: DonnaDia <37962843+DonnaDia@users.noreply.github.com>
---

diff --git a/Doc/library/subprocess.rst b/Doc/library/subprocess.rst
index 57a3285f8f4d..55dcc172bbc2 100644
--- a/Doc/library/subprocess.rst
+++ b/Doc/library/subprocess.rst
@@ -1125,6 +1125,8 @@ calls these functions.
    code was zero then return, otherwise raise :exc:`CalledProcessError`. The
    :exc:`CalledProcessError` object will have the return code in the
    :attr:`~CalledProcessError.returncode` attribute.
+   If :func:`check_call` was unable to start the process it will propagate the exception
+   that was raised.
 
    Code needing to capture stdout or stderr should use :func:`run` instead::