Move to Py_SET_TYPE from Assigning to Py_TYPE result #54
Conversation
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
Python developers have been trying to move away from assigning directly to the result of a call to Py_TYPE to using Py_SET_TYPE to accomplish the same results. The latter is now required, not just preferred.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Python developers have been trying to move away from assigning directly to the result of a call to
Py_TYPEto usingPy_SET_TYPEto accomplish the same results. The latter is now required, not just preferred.I know @gjcarneiro that you have many more important things to do, but I hope that this helps!