-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
asyncio dev docs claim that asyncio debug mode checks for unawaited coroutines #133515
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
Labels
Comments
kumaraditya303
added a commit
that referenced
this issue
May 16, 2025
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
May 16, 2025
…honGH-134081) (cherry picked from commit d94b1e9) Co-authored-by: Kumar Aditya <kumaraditya@python.org>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
May 16, 2025
…honGH-134081) (cherry picked from commit d94b1e9) Co-authored-by: Kumar Aditya <kumaraditya@python.org>
This was referenced May 16, 2025
kumaraditya303
added a commit
that referenced
this issue
May 16, 2025
kumaraditya303
added a commit
that referenced
this issue
May 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Documentation
asyncio-dev docs claim:
and the docs that points to claim:
this isn't true, python will produce warnings when coroutines are not awaited regardless of the dev mode of asyncio. The flag to set is
-Werror
and then replacesys.unraisablehook
to detect theseI think this is a hold-over from when asyncio had generator based coroutines.
Linked PRs
The text was updated successfully, but these errors were encountered: