From: Jason R. Coombs <jaraco@jaraco.com>
Date: Tue, 13 May 2014 02:40:49 +0000 (-0400)
Subject: Update docs to reflect resurrection of Setuptools over Distribute
X-Git-Tag: v3.3.6rc1~17
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=13266fb5c8e4a58c33209f8d97f86469c3245d94;p=python

Update docs to reflect resurrection of Setuptools over Distribute
---

diff --git a/Doc/library/venv.rst b/Doc/library/venv.rst
index 96ca2f5155..be0cad4231 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.