We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
event_loop
https://pytest-asyncio.readthedocs.io/en/latest/reference/fixtures/index.html#event-loop suggests that it's fine to grab event_loop fixture in a non-async function.
0.21+ migration guide in https://pytest-asyncio.readthedocs.io/en/latest/how-to-guides/migrate_from_0_21.html suggests to convert all sync functions requesting the event_loop fixture into async functions, and then acquire the loop via asyncio.get_running_loop().
asyncio.get_running_loop()
Which one is it, and what is the rationale of not depending on the event_loop fixture directly?
The text was updated successfully, but these errors were encountered:
The use of event_loop is deprecated. We should adjust the docs to reflect that. The rationale is summarized here: #706 (comment)
Sorry, something went wrong.
No branches or pull requests
https://pytest-asyncio.readthedocs.io/en/latest/reference/fixtures/index.html#event-loop suggests that it's fine to grab
event_loop
fixture in a non-async function.0.21+ migration guide in https://pytest-asyncio.readthedocs.io/en/latest/how-to-guides/migrate_from_0_21.html suggests to convert all sync functions requesting the
event_loop
fixture into async functions, and then acquire the loop viaasyncio.get_running_loop()
.Which one is it, and what is the rationale of not depending on the
event_loop
fixture directly?The text was updated successfully, but these errors were encountered: