Sourced from pytest-asyncio's releases.
pytest-asyncio 0.23.8
0.23.8 (2024-07-17)
- Fixes a bug that caused duplicate markers in async tests #813
Known issues
As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.
4be86a5
docs: Prepare release of v0.23.8.74b3a0a
Build(deps): Bump exceptiongroup in /dependencies/defaultb0009ca
[build] Declare support for Python 3.13.c747c7d
Build(deps): Bump coverage from 7.5.4 to 7.6.0 in
/dependencies/default5c40a1c
Build(deps): Bump hypothesis in /dependencies/defaultb735e8a
build: Remove development dependency on Docker.91171b4
ci: Test with CPython 3.13.d572138
Build(deps): Bump hypothesis in /dependencies/defaulta89e4d7
Build(deps): Bump certifi in /dependencies/docsb646cc1
[fix] Fixed a bug that causes markers to be duplicated for async test
functions.