summaryrefslogtreecommitdiffstats
path: root/Doc/library/venv.rst
diff options
context:
space:
mode:
authorJason R. Coombs <jaraco@jaraco.com>2014-05-13 02:41:15 (GMT)
committerJason R. Coombs <jaraco@jaraco.com>2014-05-13 02:41:15 (GMT)
commit73308d6869911d353cb58b353f64797cdba9bf0a (patch)
treef70effbc843991cf4d5769912a44a8a710c9a121 /Doc/library/venv.rst
parent08197a4616f6294e21672fd8ebb5da7ce956c8e5 (diff)
parent13266fb5c8e4a58c33209f8d97f86469c3245d94 (diff)
downloadcpython-73308d6869911d353cb58b353f64797cdba9bf0a.zip
cpython-73308d6869911d353cb58b353f64797cdba9bf0a.tar.gz
cpython-73308d6869911d353cb58b353f64797cdba9bf0a.tar.bz2
Merge doc change from 3.3
Diffstat (limited to 'Doc/library/venv.rst')
-rw-r--r--Doc/library/venv.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/library/venv.rst b/Doc/library/venv.rst
index e93f48e..e9ede8b 100644
--- a/Doc/library/venv.rst
+++ b/Doc/library/venv.rst
@@ -40,11 +40,11 @@ Creating virtual environments
A venv is a directory tree which contains Python executable files and
other files which indicate that it is a venv.
- Common installation tools such as ``Distribute`` 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
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 ``distribute_setup.py`` with the venv activated,
+ 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.