From 13266fb5c8e4a58c33209f8d97f86469c3245d94 Mon Sep 17 00:00:00 2001 From: "Jason R. Coombs" Date: Mon, 12 May 2014 22:40:49 -0400 Subject: Update docs to reflect resurrection of Setuptools over Distribute --- Doc/library/venv.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/library/venv.rst b/Doc/library/venv.rst index 96ca2f5..be0cad4 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. -- cgit v0.12