зеркало из https://github.com/mozilla/gecko-dev.git
b7b1442242
As `_run_pip()` is being removed from `VirtualenvManager` in an upcoming patch, its usages need to be removed. Besides, they're using an "internal" function, which is a bit of a smell. Note that this _could_ have been solved by exposing a public `run_pip()` function. However, I felt like that was worse because: * Friction here is good as we try to migrate the codebase to embrace the "requirements definition file" technique to install dependencies. * There could be confusion about the relationship between `install_pip_package()` (only works if venv already activated) and `_run_pip()`, which works "in general". Differential Revision: https://phabricator.services.mozilla.com/D130120 |
||
|---|---|---|
| .. | ||
| mozproxy | ||
| tests | ||
| MANIFEST.in | ||
| setup.py | ||