From 260b79185b198bad96a8fb2abc607a91ad8a5490 Mon Sep 17 00:00:00 2001 From: Michael Seifert Date: Mon, 1 Jan 2024 14:57:15 +0100 Subject: [PATCH] [docs] Prepare release of v0.23.3. Signed-off-by: Michael Seifert --- docs/source/reference/changelog.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/source/reference/changelog.rst b/docs/source/reference/changelog.rst index f00163c6..b6f57af2 100644 --- a/docs/source/reference/changelog.rst +++ b/docs/source/reference/changelog.rst @@ -2,11 +2,14 @@ Changelog ========= -0.23.3 (UNRELEASED) +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. 0.23.2 (2023-12-04)