gecko-dev/build/python-test_virtualenv_pack...

packages.txt:build/common_virtualenv_packages.txt
vendored:third_party/python/glean_parser
pypi:pytest==3.6.2
Bug 1717104: Align virtualenv_name with requirements definition r=ahal 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 2021-09-13 18:42:53 +03:00			`packages.txt:build/common_virtualenv_packages.txt`
Bug 1712151: Add test to verify virtualenv compatibility r=ahal This adds two main compatibility guarantees: 1. Vendored dependencies <=> Pypi-downloaded dependencies 2. Global Mach dependencies <=> command-specific dependencies As part of this, a new `vendored:` action was added to the virtualenv definition format. Otherwise similar to `pth:` paths, `vendored:` packages are assumed to be "pip install"-able. Some validation (the `.dist-info`/`PKG-INFO` checks) was added to `requirements.py` to verify that `pth:` and `vendored:` are correctly used. Differential Revision: https://phabricator.services.mozilla.com/D122900 2021-09-28 17:59:28 +03:00			`vendored:third_party/python/glean_parser`
Bug 1723031: Remove pytest from vendored packages r=ahal `pytest` has platform-specific dependencies (`colorama` on Windows), but our vendoring logic currently doesn't support having platform-specific packages. Since `python-test` jobs don't have to be isolated from the network, migrate `pytest` to be a `pypi:` dependency. Differential Revision: https://phabricator.services.mozilla.com/D126285 2021-09-28 23:21:39 +03:00			`pypi:pytest==3.6.2`