зеркало из https://github.com/mozilla/gecko-dev.git
55b68a8b19
We do some VCS-status processing in the background so that, if an exception occurs, we already have the file-modification information we need to decide if Sentry should receive the event. This processing can take a few seconds, especially if on a feature branch with uncommitted changes. This patch resolves the case where the Mach command finishes extremely quickly, but the VCS check takes longer. Python waits for all non-daemon processes, so by marking it as a `daemon`, Python now exits immediately once the main thread completes. Differential Revision: https://phabricator.services.mozilla.com/D128806 |
||
---|---|---|
.. | ||
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