feat(python): Update BytecodeParser
opcode awareness for upcoming Python 3.14
#23782
+32
−5
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.
It's that time of year again, when Python comes up with new bytecode ops and starts preparing to drop a new release (in early October); got a 3.14rc environment running and went through the disassembler docs to understand the new opcodes 💭
Updates
This year's release primarily adds optimising specialisations of existing ops, and it appears sufficient to make only minor updates to
RewrittenInstructions
to handle everything.For example, we can remap the following 3.14 instructions, then parse as normal:
"LOAD_FAST_BORROW" → "LOAD_FAST"
"LOAD_SMALL_INT" → "LOAD_CONST"
There is another small update for subscript access...
"BINARY_OP ([])" → "BINARY_SUBSCR"
...and another new op we can ignore:
"NOT_TAKEN"
Will keep an eye on the next release candidates, but so far this allows all
BytecodeParser
unit tests to pass 👍