I have offered before and my offer still stands to help fix this. This was already fixed in the cython main branch by Stefan. The discussion now is about when to backport it to cython 0.29.
I'm actually working on the backport now (learning cython in the process). But we will need to come up with a release plan that doesn't make me revert the cpython changes until after the 3.11 beta is released, because that would mean that I can only make them in 3.12.
On Tue, Feb 1, 2022 at 6:53 PM Miro Hrončok email@example.com wrote:
On 01. 02. 22 17:42, Victor Stinner wrote:
The problem right now is the pressure put on Cython maintainers to fix Cython as soon as possible. IMO core developers who introduce incompatible changes should be more involved in the Cython changes, since Cython is a **key component** of the Python ecosystem. IMO knowing that a change breaks Cython and relying on "the community" to fix it is not a nice move. Well, that's my opinion;-)
As the Fedora Python maintainer, I agree with this opinion. Broken Cython means we cannot actually test the next pre-release of CPython until it is fixed. And the CPython contributors who introduced the chnage are the most equipped ones to help fix it.
I understand the desire to innovate fast, but making sure Cython works should be an essential part of the innovation process (even while Cython is not part of the CPython source tree, it's part of the bigger picture).
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok
Python-Dev mailing list -- firstname.lastname@example.org To unsubscribe send an email to email@example.com https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://firstname.lastname@example.org/message/K7LZAJTG... Code of Conduct: http://python.org/psf/codeofconduct/