From: R David Murray Date: Tue, 11 Feb 2014 00:16:40 +0000 (-0500) Subject: Fix PYTHONPATH wording. It's just PATH, not "normal posix convention". X-Git-Tag: v3.4.1rc1~233^2~364 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=8dffa0e5cf0640fe7f3ca2a4940f97889397f0a8;p=thirdparty%2FPython%2Fcpython.git Fix PYTHONPATH wording. It's just PATH, not "normal posix convention". --- diff --git a/Doc/whatsnew/3.4.rst b/Doc/whatsnew/3.4.rst index ed6987645988..b1ef2775b23e 100644 --- a/Doc/whatsnew/3.4.rst +++ b/Doc/whatsnew/3.4.rst @@ -1616,14 +1616,13 @@ that may require changes to your code. Changes in 'python' command behavior ------------------------------------ -* In a posix shell, setting an environment variable to an empty value is - generally equivalent to not setting it at all. In particular, this is true - for the :envvar:`PATH` environment variable. However, setting +* In a posix shell, setting the :envvar:`PATH` environment variable to + an empty value is equivalent to not setting it at all. However, setting :envvar:`PYTHONPATH` to an empty value was *not* equivalent to not setting it at all: setting :envvar:`PYTHONPATH` to an empty value was equivalent to setting it to ``.``, which leads to confusion when reasoning by analogy to - how :envvar:`PATH` works. The behavior now conforms to the normal posix - convention. + how :envvar:`PATH` works. The behavior now conforms to the posix convention + for :envvar:`PATH`. Changes in the Python API