You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WARNING: Value for scheme.purelib does not match. Please report this to <https://github.com/pypa/pip/issues/10151>
distutils: /home/ali/.local/lib/python3.9/site-packages
sysconfig: /home/ali/.local/lib64/python3.9/site-packages
WARNING: Additional context:
user = True
home = None
root = None
prefix = None
it is 'Slackware 15.0 x86_64'
I know that there is some docker image online but never used any. The source for the python3 package > could be downloaded from https://mirrors.slackware.com/slackware/slackware64-current/source/d/python3/
will it help if I give you access to a VM running slackware 15?
PS: I gave python3-10 a try some weeks ago and pip is not usable without some manual setup.
The difference is Slackware’s Python patches purelib to use lib64 instead of lib. This is OK on its own, but Slackware needs to but did not also patch site to match this:
which causes the warning because pip correctly detects that packages installed to the incorrectly patches sysconfig locations will work (because the incorrect path is not in USER_SITE or sys.path). So Slackware should either patch site, or remove the posix_user patch in sysconfig. Fedora had a similar issue and chose to do the latter, see bpo-44860.
So the bottom line is Slackware should fix this bug. In the meantime though, I’ll submit a patch in pip to detect and slience the warning since there’s nothing pip can do in this situation.
The text was updated successfully, but these errors were encountered:
Context: #10151 (comment)
Diagnosis:
Thanks a ton @alijkl!
I just verified—this is (arguably) a bug in Slackware’s CPython patch. It patches sysconfig like this:
These are the corresponding lines in upstream CPython for comparison:
https://github.com/python/cpython/blob/v3.9.7/Lib/sysconfig.py#L69-L77
The difference is Slackware’s Python patches
purelib
to uselib64
instead oflib
. This is OK on its own, but Slackware needs to but did not also patchsite
to match this:which causes the warning because pip correctly detects that packages installed to the incorrectly patches
sysconfig
locations will work (because the incorrect path is not inUSER_SITE
orsys.path
). So Slackware should either patchsite
, or remove theposix_user
patch insysconfig
. Fedora had a similar issue and chose to do the latter, see bpo-44860.So the bottom line is Slackware should fix this bug. In the meantime though, I’ll submit a patch in pip to detect and slience the warning since there’s nothing pip can do in this situation.
The text was updated successfully, but these errors were encountered: