Author ncoghlan
Recipients barry, cjw296, doko, dstufft, ncoghlan, ned.deily, paul.moore, petr.viktorin, steve.dower
Date 2019-06-09.05:10:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Addressing the other part of Chris's initial post: there's also no `--upgrade-pip` option on `venv` itself.

Instead, there's only an `--upgrade` option that is intended for *Python* version upgrades, and restructures the internal layout of the venv to switch the Python major version number.

Unless you're using a Linux distro Python that has been patched to inject the external pip installation with rewheel or dirtbike, getting a venv that uses the externally updated version of pip requires running `python3 - m venv --system-site-packages --without-pip ...`.

So my suggestion there would be to:

- rename "venv --upgrade" to "venv --set-interpreter" (keeping `--upgrade` as a legacy alias)
- default to running `ensurepip --upgrade` with its new behaviour
- add `--network-upgrade/--no-network-upgrade` options which get passed straight through to the updated ensurepip
Date User Action Args
2019-06-09 05:10:16ncoghlansetrecipients: + ncoghlan, barry, doko, paul.moore, cjw296, ned.deily, petr.viktorin, steve.dower, dstufft
2019-06-09 05:10:16ncoghlansetmessageid: <>
2019-06-09 05:10:16ncoghlanlinkissue37107 messages
2019-06-09 05:10:16ncoghlancreate