Bug 282772 – path configuration (pth) files not processed from autoinstall directory

• Status: NEW
• Component: Tools / Tests

[Sam Sneddon [:gsnedders]]

Path configuration files are only run for site directories, and we merely add this to sys.path directly. We should instead invoke site.addsitedir, and add it as a site directory and process all path configuration files.

Currently we have:

Tools/Scripts/libraries/autoinstalled/python-3-arm64/distutils-precedence.pth
Tools/Scripts/libraries/autoinstalled/python-3-arm64/zope.interface-7.0.1-py3.9-nspkg.pth

The first of these is used to make distutils use the setuptools provided distutils with recent setuptools versions (or with env SETUPTOOLS_USE_DISTUTILS=local).

Note this doesn't actually solve Bug 261113, because that is invoking Python directly, and thus we still wouldn't treat it as a site path, as we aren't using the AutoInstaller at all.

(Also: if it were a venv, we would consider it a site directory, but it's not.)

[Radar WebKit Bug Importer]

<rdar://problem/139458740>

[Sam Sneddon [:gsnedders]]

Ah, we can't just use site.addsitedir, because we probably want to process pth files immediately after installing them, thus just using it when adding to sys.path (which we shouldn't do anyway — per bug 284088 — thus this would only be a temporary fix) doesn't suffice.