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 pitrou
Recipients barry, doko, eric.smith, koobs, martin.panter, mdk, nascheme, pitrou, twouters, vstinner, xdegaye, yan12125
Date 2018-09-27.11:13:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1538046803.04.0.545547206417.issue34814@psf.upfronthosting.co.za>
In-reply-to
Content
> Is it a real use case? Why would anyone use a RHEL binary on Debian? Debian already provides the full standard library.

I'm not talking about the standard library obviously.  I don't remember my original use case exactly, but I must have been compiling a C extension on a system and expected it to work on another.

> 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 don't believe that.  Binary wheels uploaded to PyPI seem to work fine regardless of the exact bugfix version.

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

Most wheel packages don't use the stable ABI.  They are tied to a Python version such as 2.7, but they don't differentiate between e.g. 2.7.5 and 2.7.15.  We don't break the ABI between bugfix releases.
History
Date User Action Args
2018-09-27 11:13:23pitrousetrecipients: + pitrou, twouters, barry, nascheme, doko, vstinner, eric.smith, xdegaye, martin.panter, koobs, yan12125, mdk
2018-09-27 11:13:23pitrousetmessageid: <1538046803.04.0.545547206417.issue34814@psf.upfronthosting.co.za>
2018-09-27 11:13:23pitroulinkissue34814 messages
2018-09-27 11:13:22pitroucreate