On 4/4/21 4:44 AM, Terry Reedy wrote: > On 4/3/2021 7:15 PM, Miro Hrončok wrote: >> On 03. 04. 21 21:44, Łukasz Langa wrote: >>> The memory layout of PyThreadState was unintentionally changed in the recent >>> 3.9.3 bugfix release. This leads to crashes on 32-bit systems when importing >>> binary extensions compiled for Python 3.9.0 - 3.9.2. This is a regression. >>> >>> We will be releasing a hotfix 3.9.4 around 24 hours from now to address this >>> issue and restore ABI compatibility with C extensions built for Python 3.9.0 >>> - 3.9.2. >> >> Thanks for the hotifx. >> >> However, I need to ask: Would this also happen if there was a rc version of >> 3.9.3? > > Unless the mistake was just introduced, the mistake would have happened. One > this severe would likely have been caught within the week or two before a > final. But as Łukasz noted when announcing the change, .rcs are generally > ignored.
Well, that's not true. I think for at least the past 3.8 and current 3.9 cycle I always tested the release candidates, and built them for various Linux architectures. And I'm filing issues marked as 'released-blocker' when I see regressions introduced, it's up to the release managers to determine if such changes are intended or not. Looking at the failing CI tests triggered by these builds, yes I see that 32bit archs have the ABI change. So maybe it's worth to re-introduce these RC builds, or at least provide source RC tarballs which can be tested. If it's a matter of resources, maybe fall back to quarterly subminor releases again (at least for the most current X.Y releases). Matthias _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/4TSX2OCZPOSDBB2VG26HJMUZPYZ56IL3/ Code of Conduct: http://python.org/psf/codeofconduct/
