diff options
| author | Berker Peksag <berker.peksag@gmail.com> | 2016-03-07 16:50:49 (GMT) |
|---|---|---|
| committer | Berker Peksag <berker.peksag@gmail.com> | 2016-03-07 16:50:49 (GMT) |
| commit | 777d639a923786c8ea3c527e29fcba00e764c054 (patch) | |
| tree | 0b794741cc26a5735d3ce44e5bcd00223dfdedeb /Doc | |
| parent | e525ee3b483889313b62b09b4c9103d18dd9cbb7 (diff) | |
| download | cpython-777d639a923786c8ea3c527e29fcba00e764c054.zip cpython-777d639a923786c8ea3c527e29fcba00e764c054.tar.gz cpython-777d639a923786c8ea3c527e29fcba00e764c054.tar.bz2 | |
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.
Diffstat (limited to 'Doc')
| -rw-r--r-- | Doc/library/venv.rst | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/Doc/library/venv.rst b/Doc/library/venv.rst index e9ede8b..acd1443 100644 --- a/Doc/library/venv.rst +++ b/Doc/library/venv.rst @@ -43,11 +43,6 @@ Creating virtual environments Common installation tools such as ``Setuptools`` and ``pip`` work as 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. - 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 attributes :attr:`sys.prefix` and :attr:`sys.exec_prefix` point to the base |