cythonize 0.29.x: use force=None as default instead of force=False#5712
Merged
scoder merged 1 commit intocython:0.29.xfrom Sep 21, 2023
Merged
cythonize 0.29.x: use force=None as default instead of force=False#5712scoder merged 1 commit intocython:0.29.xfrom
scoder merged 1 commit intocython:0.29.xfrom
Conversation
Contributor
Author
|
@scoder does cython still do 0.29 releases? If so, this would be helpful to have |
adamjstewart
approved these changes
Sep 21, 2023
Contributor
|
Right, that should work "better". :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I completely overlooked this in #5307,
that backport was useless because the signature of
cythonizeisin 0.29.x instead of
like it is on
3.x, meaning that settingCYTHON_FORCE_REGEN=1had no effect.