зеркало из https://github.com/mozilla/gecko-dev.git
183c94cd54
There are two sites that are allowed to define their dependencies in a flexible way: the `mach` and `build` sites. This is because these are the only two sites that _may_ have to operate without `pip install`-ing any packages, and instead having to be compatible with the packages installed to the system. Due to this required compatibility, allowing flexibility to these sites allows flexibility downstream. Anyways, this patch isn't about that - that behaviour has already landed. This patch is about tweaking `requirements.py` so that *it* doesn't care about specific sites, but rather only cares about if it should assert `only_strict_requirements` or not. Accordingly, the helpful "not all packages are pinned" error message is moved to `site.py`, where it belongs. Differential Revision: https://phabricator.services.mozilla.com/D132082 |
||
---|---|---|
.. | ||
devtools/migrate-l10n | ||
docs | ||
gdbpp/gdbpp | ||
l10n | ||
lldbutils | ||
mach | ||
mozboot | ||
mozbuild | ||
mozlint | ||
mozperftest | ||
mozrelease | ||
mozterm | ||
mozversioncontrol | ||
README | ||
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