mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-29 15:52:07 +00:00
67be954a8c
There were a bunch of locations where we were doing path shenanigans with `requirements.pth/.vendored` items. There was a bit of complexity because we were specifically making each `pthfile` line be a relative path to support moving the Firefox topsrcdir without causing issues. However, now that we're more intelligent about checking if `pthfile` lines are up-to-date (and since moving your topsrcdir will still require re-generating the Mach virtualenv), this behaviour became less useful. So, generalize `MachEnvRequirements` -> "sys.path lines" logic and reuse it everywhere. Differential Revision: https://phabricator.services.mozilla.com/D129693 |
||
|---|---|---|
| .. | ||
| 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