mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-28 15:23:51 +00:00
f782dd8f45
The Mach site is asserted to be compatible with all command sites, but command sites are deliberately //not// asserted to be compatible with each other - they're //supposed// to have the flexibility of being able to be incompatible. Accordingly, let's fail loudly if code tries to activate from one command site to another. Note that, due to the Mach site being a superset of common, it's safe to activate from "common" to "<other command site>". This is needed for cases like `./mach python --virtualenv ...`. This required updating the `mozproxy` tests, who would deliberately activate the `common` site so they could call a `mozproxy` entry point script. These tests were fixed by instead invoking `mozproxy` as a module (`-m`) of the current `python-test` site. Differential Revision: https://phabricator.services.mozilla.com/D141659 |
||
---|---|---|
.. | ||
devtools/migrate-l10n | ||
docs | ||
gdbpp/gdbpp | ||
l10n | ||
lldbutils | ||
mach | ||
mozboot | ||
mozbuild | ||
mozlint | ||
mozperftest | ||
mozrelease | ||
mozterm | ||
mozversioncontrol | ||
sites | ||
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