remove virtualenv from the pip3 install

pep-0439.txt

@@ -46,7 +46,7 @@ considerably reduced.  It is hoped that this will therefore increase
 the likelihood that Python projects will reuse third party software.
 
 The Python community also has an issue of complexity around the current
-bootstrap procedure for pip, setuptools and virtualenv. They all have
+bootstrap procedure for pip and setuptools. They all have
 their own bootstrap download file with slightly different usages and
 even refer to each other in some cases. Having a single bootstrap which
 is common amongst them all, with a simple usage, would be far preferable.
@@ -60,8 +60,8 @@ beyond requiring Python installation upgrades.
 Proposal
 ========
 
-The bootstrap will install the pip implementation, setuptools and virtualenv
-by downloading their installation files from PyPI.
+The bootstrap will install the pip implementation, setuptools by downloading
+their installation files from PyPI.
 
 This proposal affects two components of packaging: `the pip bootstrap`_ and,
 thanks to easier package installation, `modifications to publishing
@@ -77,11 +77,11 @@ The pip bootstrap
 The Python installation includes an executable called "pip3" (see PEP 394 for
 naming rationale etc.) that attempts to import pip machinery.  If it can then
 the pip command proceeds as normal.  If it cannot it will bootstrap pip by
-downloading the pip implementation, setuptools and virtualenv wheel files.
-Hereafter the installation of the "pip implementation" will imply installation
-of setuptools and virtualenv.  Once installed, the pip command proceeds as
-normal. Once the bootstrap process is complete the "pip3" command is no longer
-the bootstrap but rather the full pip command.
+downloading the pip implementation and setuptools wheel files. Hereafter the
+installation of the "pip implementation" will imply installation of setuptools
+and virtualenv.  Once installed, the pip command proceeds as normal. Once the
+bootstrap process is complete the "pip3" command is no longer the bootstrap
+but rather the full pip command.
 
 A boostrap is used in the place of a the full pip code so that we don't have
 to bundle pip and also pip is upgradeable outside of the regular Python
@@ -123,8 +123,8 @@ to PyPI.
 
 Some users may have no Internet access suitable for fetching the pip
 implementation file. These users can manually download and install the
-setuptools, virtualenv and pip tar files. Adding specific support for this
-use-case is unnecessary.
+setuptools and pip tar files. Adding specific support for this use-case is
+unnecessary.
 
 The download of the pip implementation install file will be performed
 securely.  The transport from pypi.python.org will be done over HTTPS with the
@@ -183,17 +183,17 @@ The changes to pip required by this PEP are being tracked in that project's
 issue tracker [2]_. Most notably, the addition of --bootstrap and --bootstrap-
 to-system to the pip command-line.
 
-It would be preferable that the pip, setuptools and virtualenv projects
-distribute a wheel format download.
+It would be preferable that the pip and setuptools projects distribute a wheel
+format download.
 
 The required code for this implementation is the "pip3" command described
 above. The additional pypublish can be developed outside of the scope of this
 PEP's work.
 
 Finally, it would be desirable that "pip3" be ported to Python 2.6+ to allow
-the single command to replace all existing pip, setuptools and virtualenv
-bootstrap scripts. Having that bootstrap included in a future Python 2.7
-release would also be highly desirable.
+the single command to replace existing pip, setuptools and virtualenv (which
+would be added to the bootstrap) bootstrap scripts. Having that bootstrap
+included in a future Python 2.7 release would also be highly desirable.
 
 
 Risks