зеркало из https://github.com/mozilla/gecko-dev.git
b6eb2ea22e
pip-compile can annotate each requirement with a reason why it is included (e.g.: transitive dependency, or depended-on directly). When annotating direct dependencies, it notes it as "via -r <direct path to requirements.in file>". Since we were using a temporary directory, the path of the directory was being included, making the output non-deterministic. This change ensures that we run pip-compile in the same working directory as the temporary requirements file, enabling the annotations to be deterministic: "via -r requirements-mach-vendor-python.in". Differential Revision: https://phabricator.services.mozilla.com/D72181 |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| docs | ||
| gdbpp/gdbpp | ||
| l10n | ||
| lldbutils | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozperftest | ||
| mozrelease | ||
| mozterm | ||
| mozversioncontrol | ||
| safety | ||
| 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