You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Incomplete stack traces when throwing into a generator chain that ends in a custom generator #126091
bpo-29590 identified an issue where only the head of a chain of generators was included in stack-traces when processing a thrown-in exception. I think this issue still exists but only in the case where the head of a chain of generators is a custom generator.
Consider the following example in which a custom generator's throw() method does not see its predecessor in the yield from chain (the g() generator), but the builtin in generator does:
The fix for bpo-29590 is in #19896 and appears to specifically only link frames together for chains of builtin generators only. I suspect this was just an oversight rather than a deliberate choice though.
Activity
jbower-fb commentedon Oct 30, 2024
cc @1st1 , @cjerdonek , @markshannon , and @njsmith who were involved in the first iteration of this issue.
gh-126091: Always link generator frames when propagating a thrown-in …
ZeroIntensity commentedon Jan 11, 2025
Is this done? Or was this supposed to get backported?
pythongh-126091: Always link generator frames when propagating a thro…