Sourced from pytest-asyncio's releases.
pytest-asyncio 0.23.3
0.23.3 (2024-01-01)
- Fixes a bug that caused event loops to be closed prematurely when using async generator fixtures with class scope or wider in a function-scoped test #706
- Fixes various bugs that caused an internal pytest error during test collection #711 #713 #719
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.
260b791
[docs] Prepare release of v0.23.3.6a253e2
[docs] Shorten changelog by combining multiple issues.e2cbb90
[docs] Mention correct issue in changelog.0c522bf
[fix] Fixes a bug that caused an internal pytest error when using
ImportWarni...31c7e6f
Build(deps): Bump coverage from 7.3.3 to 7.3.4 in
/dependencies/default38d5c7e
Build(deps): Bump sphinx-rtd-theme in /dependencies/docs650ec58
Build(deps): Bump babel from 2.13.1 to 2.14.0 in /dependencies/docs0166a7e
Build(deps): Bump typing-extensions in /dependencies/default3a15f30
Build(deps): Bump coverage from 7.3.2 to 7.3.3 in
/dependencies/default28e91f0
Build(deps): Bump hypothesis in /dependencies/default