On Jul 12, 2013, at 1:19 AM, Nick Coghlan <ncoghlan@gmail.com> wrote:

On 12 July 2013 15:11, Nick Coghlan <ncoghlan@gmail.com> wrote:
In particular, it establishes the infrastructure to have pyvenv automatically bootstrap the installer into each venv, even when it isn't installed system wide (which is the key missing feature of pyvenv relative to virtualenv).

The other thing I will note is that *if* we decide to add an implicit bootstrap later (which I doubt will happen, but you never know), then having "getpip" available as an importable module will also make *that* easier to write (since the heart of the current bootstrap code could be replaced by "from getpip import bootstrap")


Nick Coghlan   |   ncoghlan@gmail.com   |   Brisbane, Australia
Distutils-SIG maillist  -  Distutils-SIG@python.org

I prefer the implicit bootstrap approach, but if the explicit bootstrap approach is chosen then something special needs to be done for pyvenv. If an explicit bootstrap is required for every pyvenv then I'm going to guess that people are going to just continue using virtualenv.

Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA