[issue34814] makesetup: must link C extensions to libpython when compiled in shared mode

[STINNER Victor]

STINNER Victor <vstinner at redhat.com> added the comment:

> It means a C extension compiled with a shared-library Python cannot be imported on a monolithic Python (which doesn't have libpython.so).  It's a real problem when you want to redistribute compiled C extensions: if you compile it on RedHat/CentOS, it won't work on Ubuntu/Debian (the reverse works).

Is it a real use case? Why would anyone use a RHEL binary on Debian? Debian already provides the full standard library.

C extensions of the standard library are tidily coupled to CPython. For example, it may be dangerous to use a C extension of Python 2.7.5 on Python 2.7.15.

I'm talking about the very specific case of C extensions which are part of the stdlib.

Third party C extensions distributed as portable wheel packages using the stable ABI is different use case.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34814>
_______________________________________