-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
Test test_asyncio prints quite a few ResourceWarnings for "unclosed event loop" #99357
Labels
Comments
I'll take care of the last one in #99386 |
xiaochen7
added a commit
to xiaochen7/cpython
that referenced
this issue
Nov 12, 2022
…t_uncancel_structured_blocks
Closing event loop was missed in test_uncancel_structured_blocks, I submitted a PR #99414 to fix this : ) |
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Nov 13, 2022
…t_uncancel_structured_blocks (pythonGH-99414) (cherry picked from commit 99972dc) Co-authored-by: Xiao Chen <chenxiao_7@163.com>
Repository owner
moved this from Todo
to Done
in asyncio
Nov 13, 2022
gvanrossum
pushed a commit
that referenced
this issue
Nov 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's possible that this only happens when using
--with-pydebug
. (And perhaps only on Mac?)I get 8 of these:
There's also this, once:
The text was updated successfully, but these errors were encountered: