Skip to content
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

Fix usage of asyncio.get_event_loop which was changed in Python 3.12 to raise when no event loop was set #283

Open
sphuber opened this issue Feb 13, 2024 · 2 comments

Comments

@sphuber
Copy link
Collaborator

sphuber commented Feb 13, 2024

This is circumvented when going through a policy, which is what plumpy does, but that also raises a deprecation warning and is expected to be removed in the future.

@danielhollas
Copy link

Link to docs:

https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.get_event_loop

Code that raises the warning:

self._loop = super().get_event_loop()

@unkcpz
Copy link
Member

unkcpz commented Jan 13, 2025

I am trying to address it in #308. For our own defined policy I think we can, but the warning still raised from pytest.asyncio and nest_asyncio. I'll try to make the event loop usage more explicit and first try to get rid of the deprecated way we use get_event_loop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants