gh-109052: Use the base opcode when comparing code objects#109107
Merged
corona10 merged 3 commits intopython:mainfrom Sep 9, 2023
Merged
gh-109052: Use the base opcode when comparing code objects#109107corona10 merged 3 commits intopython:mainfrom
corona10 merged 3 commits intopython:mainfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 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.
After instrumentation, the opcode of the code object would become
INSTRUMENTED_LINEorINSTRUMENTED_INSTRUCTION, we should make sure to get the actual opcode when we compare them.This also belongs to gh-107265.