{{ message }}
gh-74929: Fix an extra DECREF for PEP 667 implementation#118583
Merged
gvanrossum merged 2 commits intoMay 5, 2024
Merged
Conversation
Member
Sorry, something went wrong.
gvanrossum
approved these changes
May 5, 2024
gvanrossum
left a comment
gvanrossum
left a comment
Member
There was a problem hiding this comment.
Maybe you want to delete or update the comment in the test?
Sorry, something went wrong.
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
Reviewers
2 participants
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.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.
In the PEP 667 implementation, when I copied the code from
_PyFrame_LocalsToFast, I did not realize thevalueis a new reference so it was decrefed in the original code. This resulted in an extra DECREF in__setitem__. Unfortunately I did not catch it because the test cases used were all immortals.Two test cases were added:
f_localsupdating itself multiple times - this will crash the interpreter without the fix