# HG changeset patch
# User Jurko Gospodnetiæ <jurko.gospodnetic@pke.hr>
# Date 1395564268 -3600
#      Sun Mar 23 09:44:28 2014 +0100
# Node ID a9681e03d52158202b50152862d3c84fe6c2a3cc
# Parent  802ed5baffb3378f8852db0cda7434c03c139e98
change venv documentation 'Distribute' reference to 'setuptools'

diff -r 802ed5baffb3 -r a9681e03d521 Doc/library/venv.rst
--- a/Doc/library/venv.rst	Sat Mar 22 20:39:08 2014 +0100
+++ b/Doc/library/venv.rst	Sun Mar 23 09:44:28 2014 +0100
@@ -40,14 +40,14 @@
    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,
-   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.
+   done by running ``setuptools`` project's ``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