This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients barry, doko, eric.smith, koobs, martin.panter, mdk, nascheme, pitrou, twouters, vstinner, xdegaye, yan12125
Date 2018-09-27.11:11:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1538046662.75.0.545547206417.issue34814@psf.upfronthosting.co.za>
In-reply-to
Content
> 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.
History
Date User Action Args
2018-09-27 11:11:02vstinnersetrecipients: + vstinner, twouters, barry, nascheme, doko, pitrou, eric.smith, xdegaye, martin.panter, koobs, yan12125, mdk
2018-09-27 11:11:02vstinnersetmessageid: <1538046662.75.0.545547206417.issue34814@psf.upfronthosting.co.za>
2018-09-27 11:11:02vstinnerlinkissue34814 messages
2018-09-27 11:11:02vstinnercreate