Mitchell Hentges 162c7ab422 Bug 1732946: Vendor pip/setuptools/wheel instead of installing into venv r=ahal ... Now that are prioritizing system over virtualenv site-packages, the system `pip` is sometimes being used instead. This is causing issues when the system pip is set up in a distro-specific way, such as when "debundled": https://github.com/pypa/pip/blob/9.0.1/pip/_vendor/__init__.py#L53-L61 However, if we vendor `pip`, `setuptools` and `wheel`, and ensure that they're prioritized in the `sys.path` before anything is imported from the system, then we can ensure that we're using a modern `pip` _and_ sidestep system-specific pip weirdness. Note that `pip-compile`'s `--allow-unsafe` flag is not as dangerous as it sounds. There's confusion among maintainers about its origin: https://github.com/jazzband/pip-tools/issues/522 Additionally, it's going to be enabled by default in a future `pip-tools` release. So, it's not scary for us to embrace here. Also, heads up that the "pip outdated warning" no longer needs to be manually silenced, since pip avoids that code path when not running from an "installed" context. Differential Revision: https://phabricator.services.mozilla.com/D127182		2021-11-01 21:34:03 +00:00
..
pip	…
pip-21.2.4.dist-info	…