Backport CYTHON_FORCE_REGEN=1 feature to 0.29 #5307
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the context of #5089, it seems like
the general opinion is that it's not a good idea to ship generated sources in
Python package release tarballs.
Right now there are tons of Python package releases that do include generated
C sources, and they may be generated from Cython versions that were not forward
compatible or had bugs. It would make sense to re-cythonize those packages with
the same minor version of cython (typically 0.29.x), without having to patch
force=True
into each and every setup.py script, especially sincesetup.py clean
is not generally defined as a command. Notice that in some cases certain packages
simply won't update their tarballs and release bugfix releases, so it would be good
to have this option.
Therefore, backport
CYTHON_FORCE_REGEN
from 3.x -> 0.29.x.