From: Georg Brandl <georg@python.org>
Date: Wed, 14 Oct 2009 15:57:46 +0000 (+0000)
Subject: #7126: os.environ changes *do* take effect in subprocesses started with os.system().
X-Git-Tag: v2.7a1~362
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=647e9d2652663b9c100be51e22fd6cfc76de95e5;p=python

#7126: os.environ changes *do* take effect in subprocesses started with os.system().
---

diff --git a/Doc/library/os.rst b/Doc/library/os.rst
index 260b3b3bf7..432de126ff 100644
--- a/Doc/library/os.rst
+++ b/Doc/library/os.rst
@@ -1836,9 +1836,9 @@ written in Python, such as a mail server's external command delivery program.
 .. function:: system(command)
 
    Execute the command (a string) in a subshell.  This is implemented by calling
-   the Standard C function :cfunc:`system`, and has the same limitations.  Changes
-   to :data:`os.environ`, :data:`sys.stdin`, etc. are not reflected in the
-   environment of the executed command.
+   the Standard C function :cfunc:`system`, and has the same limitations.
+   Changes :data:`sys.stdin`, etc. are not reflected in the environment of the
+   executed command.
 
    On Unix, the return value is the exit status of the process encoded in the
    format specified for :func:`wait`.  Note that POSIX does not specify the meaning