Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is try to force the use of custom
PlumpyEventLoopPolicy
for all tests. But in the end I can not get rid of all warnings since some are fromnest_asyncio
andpytest_asyncio
where theget_event_loop
is still used.The recommended way of replacing the
asyncio.get_event_loop
is discussed at python/cpython#100160. I made the similar change to thePlumpyEventLoopPolicy
by creating the event loop explicitly innew_event_loop
.I think the major issue came from we are using
nest_asyncio
to make event loop reentranable, which I introduced 4 years ago. Since the nest_asyncio is not actively maintained and it is not a decent way to do python asyncio, I'll look to see how to get rid of it by using the standard async primitives.