зеркало из https://github.com/mozilla/gecko-dev.git
09af1e78c9
Use `poetry` instead of `pip-compile`, then leverage `pip` to assert that there's no conflicts between environments. This enables simplifying `requirements.in`, since `colorama` is now automatically picked up, as vendoring is no longer linux-py3.6-specific. `poetry==1.2.0a2` was chosen because it was the first version that would include `pip`/`setuptools`/`wheel` in the `requirements.txt`, yet it was also the last version that supports Python 3.6 (as still used in CI in some spots). Sorry about the `requirements.txt` noise, that's because poetry doesn't sort hashes yet [1]. Fortunately, you can be confident in `requirements.txt` changes by checking that this patch doesn't include changes to vendored packages themselves (I'm including the results of a `./mach vendor python`). [1] https://github.com/python-poetry/poetry/issues/5408 Differential Revision: https://phabricator.services.mozilla.com/D142884 |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| docs | ||
| gdbpp/gdbpp | ||
| l10n | ||
| lldbutils | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozperftest | ||
| mozrelease | ||
| mozterm | ||
| mozversioncontrol | ||
| sites | ||
| 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