Repository navigation
[3.14] gh-130279: Fix missing exception handlers for jumps in loops (GH-159460) - #159703
Open
LH-and-FPGA wants to merge 2 commits into
Open
LH-and-FPGA wants to merge 2 commits into
LH-and-FPGA wants to merge 2 commits into
Conversation
…oops (pythonGH-159460) (cherry picked from commit 036d309)
LH-and-FPGA
requested review from
Eclips4,
iritkatriel and
markshannon
as code owners
October 19, 2026 11:45
This was referenced Oct 19, 2026
Open
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
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.
Manual backport of GH-159460, since the automatic cherry-pick failed.
Conflicts resolved:
Python/flowgraph.c: 3.14 doesn't have flow-graph fails to re-initialize removed instructions to 0 resulting in re-used exception handler #137681, so I kepti->i_target = NULLand only addedi->i_except = except.Lib/test/test_dis.py: regenerateddis_asyncwithon 3.14. It's the only affected case there: theNOT_TAKENbeforeRERAISEis now covered by the same handler as the precedingPOP_JUMP_IF_TRUE.Lib/test/test_monitoring.py: droppedtest_134879, which isn't on 3.14 and was pulled in by the conflict.(cherry picked from commit 036d309)
KeyboardInterruptnot handled while evaluating a tightwhileloop condition on Python 3.13 #130279