On Tue, Dec 7, 2021 at 7:55 PM Sebastian Berg <sebast...@sipsolutions.net> wrote: > One thing we once did in NumPy (for a runtime problem), was to > intentionally break everyone at pre-release/dev time to point out what > code needed fixing. Then flip the switch back at release time as to > not break production. > After a long enough time we enabled it for release mode. > > Not saying that it was nice, but it was the only alternative would have > been to never fix it. > > A similar switch could be worthwhile if it helps Victor with > experimenting on the dev-branch or reach a useful amount of projects. > Of course, I am not sure it would do either...
Py_TYPE() and Py_SIZE() macros have been converted to static inline functions in May 2020 (Python 3.10 dev cycle): https://github.com/python/cpython/commit/ad3252bad905d41635bcbb4b76db30d570cf0087 Honestly, when the change was merged, I didn't expect that it would break anything. Sadly, it broke multiple projects, including important ones like Cython and numpy. So it was reverted in Python 3.10. Once enough projects got prepared for these changes, I merged again the change in Python 3.11. Then more affected projects have been discovered. I also worked on tooling to discover affected projects before users start complaining ;-) And I wrote the PEP 674 which documents and justify these changes ;-) Victor _______________________________________________ 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/EMOJENDQVQOJQA5OHQ6OC5KCYC4PSR4A/ Code of Conduct: http://python.org/psf/codeofconduct/
