Skip to content

Commit c34da04

Browse files
committed
[docs] Mentioned pytest 8.2 compatibility fix in changelog.
Signed-off-by: Michael Seifert <[email protected]>
1 parent 143f745 commit c34da04

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

docs/source/reference/changelog.rst

+9
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,15 @@
22
Changelog
33
=========
44

5+
0.23.6 (2024-03-19)
6+
===================
7+
- Fix compatibility with pytest 8.2 `#800 <https://github.com/pytest-dev/pytest-asyncio/pull/800>`_
8+
9+
Known issues
10+
------------
11+
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.
12+
13+
514
0.23.5 (2024-02-09)
615
===================
716
- Declare compatibility with pytest 8 `#737 <https://github.com/pytest-dev/pytest-asyncio/issues/737>`_

0 commit comments

Comments
 (0)