Michael Seifert

Depends on #47

Which version of pytest-asyncio are you using? Can you provide a small example that reproduces the issue?

Pytest-asyncio still uses `asyncio.get_event_loop()`. The DeprecationWarning could be triggered by the first asyncio test in a test suite. The warning was silenced in pytest-asyncio-0.23.5, so that it doesn't affect user...

@asl97 Excellent question The way the deprecation of `asyncio.get_event_loop` was handled is unfortunate, because the function is deprecated in some patch releases and not deprecated in others. However, _get_event_loop_ is...

Pytest-asyncio v0.23.7 has been released. It includes a patch contributed by @SyntaxColoring which should resolve the issue, even with specific CPython patch versions.

@algebraist Can you provide a minimal reproducer, so we can verify if this and your issue have the same cause?

I agree that async generators should be cleaned up properly. Pytest-asyncio is currently in the middle of transitioning away from the `event_loop` fixture. You're seeing the DeprecationWarning, because users are...

This issue is no longer reproducible. It was addressed in #1034 as released in pytest-asyncio v0.25.2. @zpz Let us know if you have any further issues with this.

Thanks for the report and the reproducer! The event loop policy fixture is defined as an autouse fixture. I don't exactly recall why, but I think the reason is that...

Thanks for the report. Both is true, although they are separate issues. VectorGraphics2D is currently unmaintained. We're looking to change this, which is why VG2D is being relicensed to EPL...