-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-40975: [doc] Identify AsyncExitStack coroutine methods #20870
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
Conversation
`enter_async_context()` and `aclose()` are coroutine methods.
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.
Thanks @naglis !
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.
Good catch. Thanks!
I think NEWS can be skipped
Bump :) If there is something missing from my side, please let me know. |
closing and reopening to get a fresh testrun |
Thanks @naglis for the PR, and @iritkatriel for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.9. |
…() as coroutine methods (pythonGH-20870) (cherry picked from commit c054e8f) Co-authored-by: naglis <naglis@users.noreply.github.com>
GH-26254 is a backport of this pull request to the 3.10 branch. |
…() as coroutine methods (pythonGH-20870) (cherry picked from commit c054e8f) Co-authored-by: naglis <naglis@users.noreply.github.com>
GH-26255 is a backport of this pull request to the 3.9 branch. |
enter_async_context()
andaclose()
are coroutine methods.https://bugs.python.org/issue40975