Victor Stinner schrieb am 02.02.22 um 23:23:
On Wed, Feb 2, 2022 at 3:54 PM Stefan Behnel wrote:
So people using stable Python versions like Python 3.10 would not need Cython, but people testing the "next Python" (Python 3.11) would not have to manually removed generated C code.
That sounds like an environment variable might help?
Something like CYTHON_FORCE_REGEN=1 would be great :-)
https://github.com/cython/cython/commit/b859cf2bd72d525a724149a6e552abecf9cd... Note that this only applies when cythonize() is actually called. Some setup.py scripts may not do that unless requested to.
My use case is to use a project on the "next Python" version (the main branch) when the project contains outdated generated C code, whereas I have a more recent Cython version installed.
That use case would probably be covered by the Cython version check now, in case that stays in (the decision is pending user feedback). Stefan