mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-24 21:31:04 +00:00
9653ddb59b
Previously, when trying to determine the minimal `sys.path` that just includes the standard library (but no `pip`-installed packages), we would resolve the `sys.path` and remove the system and user site-packages. However, this "removal" step didn't work as-is for `brew`'s Python, because its "system site-packages" is //different// from its `site.getsitepackages()`. Stepping back though, there's an easier solution: run `python` with the `-S` flag, and no "site" paths or custom initialization logic will add anything extra to the stdlib. Differential Revision: https://phabricator.services.mozilla.com/D141508 |
||
---|---|---|
.. | ||
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