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 ned.deily
Recipients jd, methane, ned.deily, vstinner
Date 2020-02-29.23:19:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1583018369.63.0.124788720453.issue39599@roundup.psfhosted.org>
In-reply-to
Content
Mark:
> Or am I misunderstanding?

No, you are not misunderstanding :)

> ABI breakage shouldn't happen *at all* in bugfix releases, whether stable ABI or not.

Absolutely.

Victor:
> Julien: You cannot use the same wheel package for all Python 3.7.x versions: you need to either always compile at the installation, or ship a different wheel package per micro Python 3.7.x version.

Just to be absolutely clear here, in general you *are* supposed to be able to use the same wheel package for all 3.7.x releases (or one built for any other 3.x.x release series) as long as the extension modules in the wheel follow certain rules and the rules include don't use any Include/internal headers. If the extension module violates that restriction (as is apparently the case here), ABI compatibility across bugfix releases cannot be assured.
History
Date User Action Args
2020-02-29 23:19:29ned.deilysetrecipients: + ned.deily, vstinner, methane, jd
2020-02-29 23:19:29ned.deilysetmessageid: <1583018369.63.0.124788720453.issue39599@roundup.psfhosted.org>
2020-02-29 23:19:29ned.deilylinkissue39599 messages
2020-02-29 23:19:29ned.deilycreate