mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-12-01 17:23:59 +00:00
cba669901b
I chose to do this at the level of the outer Python invocation because: 1. `python -m cProfile ...` handles writing the file and some other details. It's possible to rebuild the functionality -- the tools are there -- but the APIs are awkward. 2. this allows to profile `mach` internals, instead of just the invoked command's implementation. This uses the return code of the `get_command` subshell to transmit the single bit of information "is the flag present". The Python-level argument is required in order to have `--help` know about the option and to avoid the `mach` shell script having to filter arguments. Differential Revision: https://phabricator.services.mozilla.com/D116151 |
||
|---|---|---|
| .. | ||
| 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