mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-24 21:31:04 +00:00
18645cf2ae
There are cases in CI where we're using the system Python, but we still want to create a virtualenv. For example, build jobs use the system Python packages, but Mozharness wants to have access to Mach packages. So, a virtualenv needs to be created (the `"common"` virtualenv), whose associated `python` binary is used to invoke Mozharness. So, just like for the `build` site, allow creating the `common` site even when the "native package source" is the system Python. Since `mach_virtualenv_requirements.txt` already depends on `common_virtualenv_requirements.txt`, this restriction should not cause validation breakage. Differential Revision: https://phabricator.services.mozilla.com/D140255 |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| docs | ||
| gdbpp/gdbpp | ||
| l10n | ||
| lldbutils | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozperftest | ||
| mozrelease | ||
| mozterm | ||
| mozversioncontrol | ||
| mach_commands.py | ||
| moz.build | ||
| README | ||
This directory contains common Python code. The basic rule is that if Python code is cross-module (that's "module" in the Mozilla meaning - as in "module ownership") and is MPL-compatible, it should go here. What should not go here: * Vendored python modules (use third_party/python instead) * Python that is not MPL-compatible (see other-licenses/) * Python that has good reason to remain close to its "owning" (Mozilla) module (e.g. it is only being consumed from there). Historical information can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=775243 https://bugzilla.mozilla.org/show_bug.cgi?id=1346025