On 10 July 2013 19:55, Vinay Sajip <vinay_sajip@yahoo.co.uk> wrote:
Richard Jones <richard <at> python.org> writes:
It makes sense to me (and Nick) to simplify the packaging overhead for users of Python 2. Currently the story is a bit of a mess (multiple sites with different approaches).
No argument there, but I still don't see the relevance of virtualenv in a 3.4+ context. The PEP states
"Hereafter the installation of the 'pip implementation' will imply installation of setuptools and virtualenv."
Sorry I've not made this clearer. Per the discussion here I've removed that from the PEP. That version hasn't been built on the web server yet.
Exactly what benefit does including virtualenv provide in a 3.4+ installation?
That was kinda my question <wink>
Sorry, it didn't come across like a question, more like a fait accompli :-)
Poorly phrased, my apologies. Richard