classification
Title: distutils.sysconfig.get_python_lib() does not respect sysconfig/distutils install schemes
Type: Stage:
Components: Distutils Versions: Python 3.11
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: FFY00, dstufft, eric.araujo, frenzy, hroncok, jaraco, petr.viktorin, vstinner
Priority: normal Keywords:

Created on 2021-10-13 14:02 by hroncok, last changed 2021-10-18 10:17 by frenzy.

Messages (2)
msg403834 - (view) Author: Miro Hrončok (hroncok) * Date: 2021-10-13 14:02
In https://github.com/python/cpython/pull/24549 (Load install schemes from sysconfig) we have assumed that distutils will simply read all information from sysconfig, so distributors could patch the install schemes in there and distutils (whether the one in the standard library or a third party fork).

However, in https://github.com/pypa/pip/issues/10151#issuecomment-942162384 we have figured out that distutils.sysconfig.get_python_lib() does not respect the schemes from sysconfig at all, instead, it creates the paths from scratch.

This might be too late for Python 3.10, but in Python 3.11 I'd like distutils.sysconfig.get_python_lib() to return paths defined by sysconfig install schemes. That way, we can more easily move that from the standard library to a third-party project with an independent delivery mechanism.
msg403836 - (view) Author: Miro Hrončok (hroncok) * Date: 2021-10-13 14:04
> so distributors could patch the install schemes in there and distutils (whether the one in the standard library or a third party fork).

Somehow, this sentence is not finished properly.

...so distributors could patch the install schemes in there and distutils (whether the one in the standard library or a third party fork) would respect it.
History
Date User Action Args
2021-10-18 10:17:17frenzysetnosy: jaraco, vstinner, eric.araujo, petr.viktorin, dstufft, hroncok, frenzy, FFY00
2021-10-13 14:04:36hroncoksetmessages: + msg403836
2021-10-13 14:02:39hroncokcreate