summaryrefslogtreecommitdiffstats
path: root/Doc/whatsnew
diff options
context:
space:
mode:
authorR David Murray <rdmurray@bitdance.com>2014-02-11 00:16:40 (GMT)
committerR David Murray <rdmurray@bitdance.com>2014-02-11 00:16:40 (GMT)
commit8dffa0e5cf0640fe7f3ca2a4940f97889397f0a8 (patch)
tree4c87faf7eedddcfedbf7f3da34cadfc5c5955a40 /Doc/whatsnew
parent96eeddba0542f0b5323659ffb0fa7038032899d8 (diff)
downloadcpython-8dffa0e5cf0640fe7f3ca2a4940f97889397f0a8.zip
cpython-8dffa0e5cf0640fe7f3ca2a4940f97889397f0a8.tar.gz
cpython-8dffa0e5cf0640fe7f3ca2a4940f97889397f0a8.tar.bz2
Fix PYTHONPATH wording. It's just PATH, not "normal posix convention".
Diffstat (limited to 'Doc/whatsnew')
-rw-r--r--Doc/whatsnew/3.4.rst9
1 files changed, 4 insertions, 5 deletions
diff --git a/Doc/whatsnew/3.4.rst b/Doc/whatsnew/3.4.rst
index ed69876..b1ef277 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