-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh-111058: Change coro.cr_frame/gen.gi_frame to be None for a closed coroutine/generator. #112428
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Maybe we need more general NEWS
entry because the issue applies not only to coroutines but also to generators?
Misc/NEWS.d/next/Core and Builtins/2023-11-26-21-30-11.gh-issue-111058.q4DqDY.rst
Outdated
Show resolved
Hide resolved
Misc/NEWS.d/next/Core and Builtins/2023-11-26-21-30-11.gh-issue-111058.q4DqDY.rst
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks for fixing this.
Thanks @iritkatriel for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12. |
GH-112589 is a backport of this pull request to the 3.12 branch. |
…losed coroutine/generator. (pythonGH-112428) (cherry picked from commit bfb576e) Co-authored-by: Irit Katriel <1055913+iritkatriel@users.noreply.github.com>
…losed coroutine/generator. (python#112428)
…losed coroutine/generator. (python#112428)
Fixes #111058.
getcoroutinestate
returns the wrong state. #111058