libpython3.so does not link to libpython3.x.so.y.z since python 3.11
Task Info (Flyspray) | |
---|---|
Opened By | Yichao Yu (yuyichao) |
Task ID | 80136 |
Type | Bug Report |
Project | Arch Linux |
Category | Upstream Bugs |
Version | None |
OS | All |
Opened | 2023-11-02 01:30:18 UTC |
Status | Assigned |
Assignee | David Runge (dvzrv) |
Assignee | Felix Yan (felixonmars) |
Details
Description:
Python provides a version specific library with the soname libpython3.x.so.y.z (for python 3.11 this is currently libpython3.11.so.1.0) that contains the actual implementation of basically everything as well as a ABI-stable (https://peps.python.org/pep-0384/) library libpython3.so that conforming libraries can link to. Accessing the latter should allow accessing symbols from the former. AFAICT, the way this is implemented is that libpython3.so links to libpython3.x.so.y.z so it pulls in the real library when loaded. This is indeed the case up to the latest 3.10 version package but is not the case anymore for any of the 3.11 packages. This causes applications that loads libpython3.so to not work anymore.
Additional info:
- package version(s)
- config and/or log files etc.
- link to upstream bug report, if any
Steps to reproduce:
run objdump -p /usr/lib/libpython3.so
and see that it doesn't link to the actual python library anymore.