[Distutils] PEP 453 quirk: pyvenv --no-download with an upgraded system pip

[Oscar Benjamin]

On 18 September 2013 15:26, Nick Coghlan <ncoghlan at gmail.com> wrote:
> In creating the next draft of PEP 453, I noticed an odd quirk of the
> proposed "pyvenv --no-download" option: it bootstraps the version of
> pip *that was provided with Python*, rather than the version currently
> installed in the base Python installation.
>
> That seems incredibly strange to me, and I expect it will confuse
> users as well. "I'm using Python 3.4 and have upgraded pip to 1.6, but
> my virtual environments are only getting pip 1.5 when I use the
> '--no-download' option. HALP!".

Could the getpip script have a way to update its internal/bundled pip
when updating the other pip? Or perhaps an explicit update bundle
command?

Could getpip be the recommended way to update pip/setuptools generally
(perhaps solving some of the other problems that can occur) and always
update its bundle?


Oscar