mirror of https://github.com/python/cpython
Fix PYTHONPATH wording. It's just PATH, not "normal posix convention".
This commit is contained in:
parent
96eeddba05
commit
8dffa0e5cf
|
@ -1616,14 +1616,13 @@ that may require changes to your code.
|
||||||
Changes in 'python' command behavior
|
Changes in 'python' command behavior
|
||||||
------------------------------------
|
------------------------------------
|
||||||
|
|
||||||
* In a posix shell, setting an environment variable to an empty value is
|
* In a posix shell, setting the :envvar:`PATH` environment variable to
|
||||||
generally equivalent to not setting it at all. In particular, this is true
|
an empty value is equivalent to not setting it at all. However, setting
|
||||||
for the :envvar:`PATH` environment variable. However, setting
|
|
||||||
:envvar:`PYTHONPATH` to an empty value was *not* equivalent to not setting it
|
: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
|
at all: setting :envvar:`PYTHONPATH` to an empty value was equivalent to
|
||||||
setting it to ``.``, which leads to confusion when reasoning by analogy 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
|
how :envvar:`PATH` works. The behavior now conforms to the posix convention
|
||||||
convention.
|
for :envvar:`PATH`.
|
||||||
|
|
||||||
|
|
||||||
Changes in the Python API
|
Changes in the Python API
|
||||||
|
|
Loading…
Reference in New Issue