summaryrefslogtreecommitdiffstats
path: root/Doc/library/venv.rst
diff options
context:
space:
mode:
Diffstat (limited to 'Doc/library/venv.rst')
-rw-r--r--Doc/library/venv.rst5
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