This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients FFY00, frenzy, hroncok, jaraco, steve.dower
Date 2021-05-03.16:58:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Making sysconfig look at sitecustomize seems like the wrong approach.

I mean, you're literally customizing the site, so having it be done from sitecustomize doesn't seem terribly wrong. But I agree, I'd rather see the code in sitecustomize poke paths into sysconfig, rather than the other way around.

The problem then would be that -S bypasses the path configuration entirely, which is likely going to point at non-existent paths. So yeah, for this case you need an override that isn't tied to the site module. Having a similar-but-different mechanism in sysconfig seems fine. I have a *slight* preference for non-executable code, mostly to avoid the risk of import hijacking, but it's only slight.
Date User Action Args
2021-05-03 16:58:11steve.dowersetrecipients: + steve.dower, jaraco, hroncok, frenzy, FFY00
2021-05-03 16:58:11steve.dowersetmessageid: <>
2021-05-03 16:58:11steve.dowerlinkissue43976 messages
2021-05-03 16:58:11steve.dowercreate