* Class-scoped and module-scoped event loops can be requested via the _asyncio_event_loop_ mark. [620](https://github.com/pytest-dev/pytest-asyncio/pull/620) * Deprecate redefinition of the _event_loop_ fixture. [587](https://github.com/pytest-dev/pytest-asyncio/issues/531) Users requiring a class-scoped or module-scoped asyncio event loop for their tests should mark the corresponding class or module with _asyncio_event_loop_. * Test items based on asynchronous generators always exit with _xfail_ status and emit a warning during the collection phase. This behavior is consistent with synchronous yield tests. [642](https://github.com/pytest-dev/pytest-asyncio/issues/642) * Remove support for Python 3.7 * Declare support for Python 3.12
0.21.2
- Fix compatibility with pytest 8.2. Backport of [800](https://github.com/pytest-dev/pytest-asyncio/pull/800) to pytest-asyncio v0.21 for users who are unable to upgrade to a more recent version (see [#706](https://github.com/pytest-dev/pytest-asyncio/pull/706)
0.21.1
* Output a proper error message when an invalid `asyncio_mode` is selected. * Extend warning message about unclosed event loops with additional possible cause. 531 * Previously, some tests reported "skipped" or "xfailed" as a result. Now all tests report a "success" result.