➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients dstufft, loewis, ncoghlan, ned.deily, vinay.sajip
Date 2013-10-22.13:41:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1382449311.41.0.705897907061.issue19347@psf.upfronthosting.co.za>
In-reply-to
Content 
Check PEP 453 again: http://www.python.org/dev/peps/pep-0453/#changes-to-virtual-environments

Rather than only changing pyvenv, the API in the PEP is to add "with_pip" parameters to the venv module API, so that anyone building pyvenv style tools on top of venv can easily request installation of pip by passing "with_pip=True". The change to pyvenv is then to just add the --without-pip flag (since the default is inverted for the two interfaces - library API is opt-in for backwards compatibility, tool CLI is opt-out)
History
Date User Action Args
2013-10-22 13:41:51ncoghlansetrecipients: + ncoghlan, loewis, vinay.sajip, ned.deily, dstufft
2013-10-22 13:41:51ncoghlansetmessageid: <1382449311.41.0.705897907061.issue19347@psf.upfronthosting.co.za>
2013-10-22 13:41:51ncoghlanlinkissue19347 messages
2013-10-22 13:41:51ncoghlancreate