[issue29590] Incorrect stack traces when re-entering a generator/coroutine stack via .throw()

Change by Irit Katriel : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue29590] Incorrect stack traces when re-entering a generator/coroutine stack via .throw()

miss-islington added the comment: New changeset e92219d8f864a1a8eb381d98d5df4f1aa767dacb by Miss Islington (bot) in branch '3.9': bpo-29590: fix stack trace for gen.throw() with yield from (GH-19896) https://github.com/python/cpython/commit/e92219d8f864a1a8eb381d98d5df4f1aa767dacb

[issue29590] Incorrect stack traces when re-entering a generator/coroutine stack via .throw()

Change by miss-islington : -- pull_requests: +21191 pull_request: https://github.com/python/cpython/pull/22106 ___ Python tracker ___

[issue29590] Incorrect stack traces when re-entering a generator/coroutine stack via .throw()

Change by miss-islington : -- nosy: +miss-islington nosy_count: 3.0 -> 4.0 pull_requests: +20565 pull_request: https://github.com/python/cpython/pull/21416 ___ Python tracker

[issue29590] Incorrect stack traces when re-entering a generator/coroutine stack via .throw()

Mark Shannon added the comment: New changeset 8b33961e4bc4020d8b2d5b949ad9d5c669300e89 by Chris Jerdonek in branch 'master': bpo-29590: fix stack trace for gen.throw() with yield from (#19896) https://github.com/python/cpython/commit/8b33961e4bc4020d8b2d5b949ad9d5c669300e89 --

[issue29590] Incorrect stack traces when re-entering a generator/coroutine stack via .throw()

Chris Jerdonek added the comment: I just filed a related issue to this that's also similar to issue 29587: https://bugs.python.org/issue40694 -- ___ Python tracker ___

[issue29590] Incorrect stack traces when re-entering a generator/coroutine stack via .throw()

Chris Jerdonek added the comment: I proposed a PR to fix this: https://github.com/python/cpython/pull/19896 -- ___ Python tracker ___

[issue29590] Incorrect stack traces when re-entering a generator/coroutine stack via .throw()

Change by Chris Jerdonek : -- keywords: +patch pull_requests: +19207 stage: -> patch review pull_request: https://github.com/python/cpython/pull/19896 ___ Python tracker ___

[issue29590] Incorrect stack traces when re-entering a generator/coroutine stack via .throw()

Change by Chris Jerdonek : -- versions: +Python 3.8, Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue29590] Incorrect stack traces when re-entering a generator/coroutine stack via .throw()

Change by Chris Jerdonek : -- nosy: +chris.jerdonek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue29590] Incorrect stack traces when re-entering a generator/coroutine stack via .throw()

Changes by Mariatta Wijaya : -- components: +Interpreter Core ___ Python tracker ___

[issue29590] Incorrect stack traces when re-entering a generator/coroutine stack via .throw()

New submission from Nathaniel Smith: The attached script sets up a stack of generators calling each other via 'yield from': f yields from g yield from h. Then the generator at the bottom of the stack yields. Before they yield, sys._getframe shows the expected stack (or if you put in