зеркало из https://github.com/mozilla/gecko-dev.git
75d14b24c3
Maps virtualenvs one-to-one with their associated requirements definition. For example: ``` Name: "docs" Virtualenv location: <snip>/_virtualenvs/docs Requirements location: $topsrcdir/build/docs_virtualenv_packages.txt ``` An issue to be resolved in the future is that it's tricky to know that, when you define a new virtualenv, you have to *know* that a requirements definition needs to exist in `build/`. As part of this change, the default virtualenv ("common") was split from the build virtualenv ("build"). This required changes to the python-test virtualenv since python-tests depend on `glean_parser`, but were getting it implicitly from the "build" virtualenv's requirements. This addition to the `python-test` virtualenv is temporary and will be removed when bug 1724273 is resolved. Differential Revision: https://phabricator.services.mozilla.com/D122891 |
||
---|---|---|
.. | ||
docker-image | ||
github-sync | ||
liblowercase | ||
mach | ||
mozharness | ||
perftest | ||
profile-generate | ||
push-to-try | ||
sphinx-docs | ||
taskgraph | ||
toolchain-build | ||
tps | ||
update-verify | ||
upload-generated-sources | ||
upload-symbols | ||
webrender |