mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-12-11 08:13:35 +00:00
e9b6ee396c
On newer systems, Python is intelligently populating pure-python and platform-specific packages into //two different directories//. Traditionally, these directories would be symlinked - or only one would exist. However, to support these newer systems (and be better integrated with Python conventions), we should handle both of these directories properly. The solution here is, when calculating the `site_packages_dir()`, calculate all of them, and handle the multitude at all call sites. The one use case where we want only one path (the resolving the location for the `mach.pth` pthfile), I've opted for the `platlib`, since both pure python dependencies //and// platform-specific dependencies are referenced by the pthfile. Differential Revision: https://phabricator.services.mozilla.com/D140870 |
||
|---|---|---|
| .. | ||
| 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