8000
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
e49365f
49cfa81
3a3d5e2
60dafa1
16f1c4e
c8ae89d
8229efc
6473022
02190f2
9607d8e
dad94d9
6e56155
1037078
4e69faf
740e0c2
7721ea1
f4f6fc5
cad5231
5647edb
102ba29
de21df0
d30824f
978c822
fbeb1a7
6fe4985
592fcb9
d27f174
871507f
5dfc542
a4fac11
fc2e400
65a2db6
d25f852
…ory does not
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
asyncio.new_event_loop is the default value, so why pass it at all?
asyncio.new_event_loop
Sorry, something went wrong.
Ah well about that...
This is extremely confusing asyncio behavior that I strongly disagree with https://github.com/python/cpython/pull/94593/files#r914528655
passing the loop factory disables the calls to set the asyncio.set_event_loop()
asyncio.set_event_loop()