Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 8dffa0e

Browse files
committed
Fix PYTHONPATH wording. It's just PATH, not "normal posix convention".
1 parent 96eeddb commit 8dffa0e

1 file changed

Lines changed: 4 additions & 5 deletions

File tree

Doc/whatsnew/3.4.rst

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1616,14 +1616,13 @@ that may require changes to your code.
16161616
Changes in 'python' command behavior
16171617
------------------------------------
16181618

1619-
* In a posix shell, setting an environment variable to an empty value is
1620-
generally equivalent to not setting it at all. In particular, this is true
1621-
for the :envvar:`PATH` environment variable. However, setting
1619+
* In a posix shell, setting the :envvar:`PATH` environment variable to
1620+
an empty value is equivalent to not setting it at all. However, setting
16221621
:envvar:`PYTHONPATH` to an empty value was *not* equivalent to not setting it
16231622
at all: setting :envvar:`PYTHONPATH` to an empty value was equivalent to
16241623
setting it to ``.``, which leads to confusion when reasoning by analogy to
1625-
how :envvar:`PATH` works. The behavior now conforms to the normal posix
1626-
convention.
1624+
how :envvar:`PATH` works. The behavior now conforms to the posix convention
1625+
for :envvar:`PATH`.
16271626

16281627

16291628
Changes in the Python API

0 commit comments

Comments
 (0)