Message392823
> 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:11 | steve.dower | set | recipients:
+ steve.dower, jaraco, hroncok, frenzy, FFY00 |
2021-05-03 16:58:11 | steve.dower | set | messageid: <1620061091.91.0.33451519206.issue43976@roundup.psfhosted.org> |
2021-05-03 16:58:11 | steve.dower | link | issue43976 messages |
2021-05-03 16:58:11 | steve.dower | create | |
|