[3.10] gh-93592: Fix frame chain when throwing exceptions into coroutines #95207
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.
Issue #93592 describes how a
coro.throw()
will wake up the coroutine, but the frame chain is broken, making itimpossible to get a proper traceback. This impedes debuggers when they break on thrown exceptions, among other things.
The problem is observed in versions
3.7
-3.10
but is fixed in3.11
, since there appears to have been structural changes made in frame objects in that version, and the necessary re-write of the generator code seems to have (accidentally?) fixed the issue.A regression tests is provided, which could also be applied to the
3.11
andmain
branches.