Closed samypr100 closed 1 year ago
yeah this is probably some weirdness with the sysconfig rewrite that happened in 3.10
although, the debian patch here kinda looks like a mistake cc @stefanor -- I expect a unix_local
scheme to have local
for include as well (it has it for headers
)
https://bugs.debian.org/1007966 ?
Fixed in https://salsa.debian.org/cpython-team/python3/-/commit/7e712c8f1bbdc562ed228adb6f675eb277034576
And with an update to python3-stdlib-extensions
, because distutils is shipped separately.
I've copied the sysconfig dicts from debian -- this should resolve in a few hours once launchpad finishes building
description
After installing
python3.10-dev
orpython3.11-dev
, noticed thatsysconfig
module on python 3.10 and python 3.11 builds shows the wronginclude
, andplatinclude
path being/usr/local/include/python3.X
when the actual location of the headers is in/usr/include/python3.X
since/usr/local/include/python3.X
is actually empty.^ Should output
/usr/include/python3.10
^ Should output
/usr/include/python3.11
This seems like a non-issue on python 3.9 and below as it reports the correct path, namely
/usr/include/python3.X
for deadsnakes builds. I checked python 3.8 as well and it was correct.Similarly, on the python provided by upstream debian (e.g. jammy), Python 3.10 reports correctly
/usr/include/python3.X
, so it seems something isolated to deadsnakes build for some reason.os information
lsb_release -a
uname -a