traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Issue #21034: Remove outdated paragraph from venv documentation 

Since Python 3.4, there is no need to install pip and setuptools
into a venv manually.
This commit is contained in:
Berker Peksag 2016-03-07 18:51:06 +02:00
parent 20b3e72b8d 777d639a92
commit 5b96d66ac6
1 changed files with 0 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Doc/library/venv.rst
View File

@ -43,11 +43,6 @@ Creating virtual environments
Common installation tools such as ``Setuptools`` and ``pip`` work as Common installation tools such as ``Setuptools`` and ``pip`` work as
expected with venvs - i.e. when a venv is active, they install Python expected with venvs - i.e. when a venv is active, they install Python
packages into the venv without needing to be told to do so explicitly. packages into the venv without needing to be told to do so explicitly.
Of course, you need to install them into the venv first: this could be
done by running ``ez_setup.py`` with the venv activated,
followed by running ``easy_install pip``. Alternatively, you could download
the source tarballs and run ``python setup.py install`` after unpacking,
with the venv activated.
When a venv is active (i.e. the venv's Python interpreter is running), the When a venv is active (i.e. the venv's Python interpreter is running), the
attributes :attr:`sys.prefix` and :attr:`sys.exec_prefix` point to the base attributes :attr:`sys.prefix` and :attr:`sys.exec_prefix` point to the base