Minor tweaks to PEP 405.
This commit is contained in:
parent
322d7df21a
commit
e071a3e683
18
pep-0405.txt
18
pep-0405.txt
|
@ -173,7 +173,6 @@ This is not strictly necessary for use of a virtual environment (as an
|
||||||
explicit path to the venv's python binary or scripts can just as well
|
explicit path to the venv's python binary or scripts can just as well
|
||||||
be used), but it is convenient.
|
be used), but it is convenient.
|
||||||
|
|
||||||
The ``venv`` module also adds a ``pysetup3`` script into each venv.
|
|
||||||
In order to allow ``pysetup`` and other Python package managers to
|
In order to allow ``pysetup`` and other Python package managers to
|
||||||
install packages into the virtual environment the same way they would
|
install packages into the virtual environment the same way they would
|
||||||
install into a normal Python installation, and avoid special-casing
|
install into a normal Python installation, and avoid special-casing
|
||||||
|
@ -202,7 +201,7 @@ While on a Windows system::
|
||||||
|
|
||||||
Third-party packages installed into the virtual environment will have
|
Third-party packages installed into the virtual environment will have
|
||||||
their Python modules placed in the ``site-packages`` directory, and
|
their Python modules placed in the ``site-packages`` directory, and
|
||||||
their executables placed in ``bin/`` or ``Scripts\``.
|
their executables placed in ``bin/`` or ``Scripts``.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
|
@ -407,9 +406,10 @@ than ``sys.site_prefix`` or the appropriate ``site`` API to find
|
||||||
site-packages directories.
|
site-packages directories.
|
||||||
|
|
||||||
The most notable case is probably `setuptools`_ and its fork
|
The most notable case is probably `setuptools`_ and its fork
|
||||||
`distribute`_, which mostly use ``distutils``/``sysconfig`` APIs, but
|
`distribute`_, which mostly use ``distutils``and ``sysconfig`` APIs,
|
||||||
do use ``sys.prefix`` directly to build up a list of site directories
|
but do use ``sys.prefix`` directly to build up a list of site
|
||||||
for pre-flight checking where ``pth`` files can usefully be placed.
|
directories for pre-flight checking where ``pth`` files can usefully
|
||||||
|
be placed.
|
||||||
|
|
||||||
Otherwise, a `Google Code Search`_ turns up what appears to be a
|
Otherwise, a `Google Code Search`_ turns up what appears to be a
|
||||||
roughly even mix of usage between packages using ``sys.prefix`` to
|
roughly even mix of usage between packages using ``sys.prefix`` to
|
||||||
|
@ -503,14 +503,6 @@ to not require that Xcode is installed.
|
||||||
.. _Virtualenv uses: https://github.com/pypa/virtualenv/issues/168
|
.. _Virtualenv uses: https://github.com/pypa/virtualenv/issues/168
|
||||||
|
|
||||||
|
|
||||||
Provide a mode that is isolated only from user site packages?
|
|
||||||
-------------------------------------------------------------
|
|
||||||
|
|
||||||
Is there sufficient rationale for providing a mode that isolates the
|
|
||||||
venv from :pep:`370` user site packages, but not from the system-level
|
|
||||||
site-packages?
|
|
||||||
|
|
||||||
|
|
||||||
Other Python implementations?
|
Other Python implementations?
|
||||||
-----------------------------
|
-----------------------------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue