Tell people to report sysconfig issues to Apple #10707
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I’ve been ignoring this for a while becase it is extremely poor practice to install pip against an Xcode-installed Python, but this has been popping up much more frequently in #10151 for some reason that I feel we should do something about it. This Apple bug is actually quite serious. This is how the warnings look like:
The warnign appear when the prefix is an overlay i.e. when pip is doing build isolation. The result is that, if Apple ships Python 3.10 with the same patch, pip will fail to correctly perform build isolation because sysconfig won’t install build backends to the overlay, but to
/Library/Python
. This patch suppresses the current warning, and emit a new one telling users clearly that Apple is the problem and how they can help. (From what I know, bugs reproted to Apple’s public platform tend to go into a void, but that’s the best we can do.)