mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-24 21:31:04 +00:00
e913081903
In addition to showing the `pip check` failure, also show: * The `pip install --requirements ...` output * The output of `pip list -v` * The path to the `requirements.txt` file and the affected site. To get sufficient detail of `pip install --requirements` to display if the subsequent `pip check` call failed, I had to remove the `--quiet` parameter. It was replicated by hiding _all_ output if `quiet=True` and `pip install` succeeds - this is different to the previous behaviour, where warnings would still poke through, even if `quiet=True` and the install succeeded. This was the only way to make it work such that all output would be available without having to run `pip install` twice (which would likely get different output the second time). Besides, there weren't many warnings triggering this edge case, so the change in behaviour is probably acceptable. Additionally, in both places doing `pip check` (post-install-requirements and when doing system-package compatibility checking), move the `pip check` output to happen last, so that users don't need to scroll to the top of the `pip list` wall of text to find the reason for their command failure. Differential Revision: https://phabricator.services.mozilla.com/D137206 |
||
---|---|---|
.. | ||
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