Work around Debian bug in get_python_lib() #10255
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.
#10151 (comment)
#10151 (comment)
#10151 (comment)
#10151 (comment)
#10217 (comment)
@siddhpant @Molkree @pdxjohnny @KanTakahiro
It turns out this is a bug in Debian’s
distutils.sysconfig.get_python_lib()
implementation. This function is called when pip builds a package from source (to create a build-time isolated environment), so it does not happen when you install a wheel (or when installing a package from source for a second time, because pip would cache the previously-built wheel). This patch basically just tries to detect that bug and pretend nothing happens when it triggers the warning.Please give this a try and tell me if it can correctly suppress the warning.