MAINT/BUG: Followups for PySequence_Fast locking #29405
Merged
+37
−48
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.
Followup for #29394.
Removes the
NO_BRACKETS
variants for the critical section macros that I added in #29394. This allows us to diverge from the coding style in CPython a little less.I initially thought this would be purely a refactor, but I noticed some bugs to fix as well. The
BEGIN_CRITICAL_SECTION_SEQUENCE_FAST
macro accepts the argument toPySequence_Fast
, not the object returned by it. I incorrectly used it on the object returned byPySequence_Fast
in a few spots in #29394.Each commit is fairly atomic and explains what it does, so probably best to review commit-by-commit.