mirror of
https://github.com/HeyPuter/firefox.git
synced 2026-11-15 17:55:15 -10:00
Now that we are gleaning a site packages source in a process-global way (that is *not* conditional on the site that's being managed), we've removed an edge case from occurring: the case where Mach would use `SitePackagesSource.NONE`, but the command site would use `SitePackagesSource.SYSTEM`. This would've occurred if none of Mach's dependencies were found in the system Python, but instead once the command site was initialized, one of *its* dependencies were located. Since that can no longer happen: * Command sites that don't populate their VENV will *always* use the same site packages source as Mach * `pthfile` generation is simplified (the priority of the system paths is no longer variable) * We no longer need to track `site_packages_source` in metadata, since we can use `mach_site_packages_source` instead. While here, I moved the "`PIP_NETWORK_INSTALL_RESTRICTED_VIRTUALENVS` sites shouldn't have `pypi_requirements`" check to a test, since there's no need for it to happen at runtime. Differential Revision: https://phabricator.services.mozilla.com/D140668
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