Log message:
py-test-asyncio: updated to 0.25.0

0.25.0 (2024-12-13)

Deprecated: Added warning when asyncio test requests async @pytest.fixture in \ 
strict mode. This will become an error in a future version of flake8-asyncio.
Updates the error message about pytest.mark.asyncio's scope keyword argument to \ 
say loop_scope instead.
Verbose log displays correct parameter name: asyncio_default_fixture_loop_scope
Propagates contextvars set in async fixtures to other fixtures and tests on \ 
Python 3.11 and above.

Log message:
py-*: remove unused tool dependency

py-setuptools includes the py-wheel functionality nowadays

Log message:
py-test-asyncio: updated to 0.24.0

0.24.0 (2024-08-22)

- BREAKING: Updated minimum supported pytest version to v8.2.0
- Adds an optional `loop_scope` keyword argument to `pytest.mark.asyncio`. This \ 
argument controls which event loop is used to run the marked async test.
- Deprecates the optional `scope` keyword argument to `pytest.mark.asyncio` for \ 
API consistency with ``pytest_asyncio.fixture``. Users are encouraged to use the \ 
`loop_scope` keyword argument, which does exactly the same.
- Raises an error when passing `scope` or `loop_scope` as a positional argument \ 
to ``@pytest.mark.asyncio``.
- Fixes a bug that caused module-scoped async fixtures to fail when reused in \ 
other modules

Log message:
py-test-asyncio: updated to 0.23.8

0.23.8 (2024-07-17)

- Fixes a bug that caused duplicate markers in async tests
- Declare support for Python 3.13

Log message:
py-test-asyncio: updated to 0.23.7

0.23.7 (2024-05-19)

- Silence deprecation warnings about unclosed event loops that occurred with \ 
certain CPython patch releases

Log message:
py-test-asyncio: updated to 0.23.6

0.23.6 (2024-03-19)
===================
- Fix compatibility with pytest 8.2

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. 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.

Log message:
py-test-asyncio: updated to 0.23.5

0.23.5 (2024-02-09)
===================
- Declare compatibility with pytest 8
- Fix typing errors with recent versions of mypy
- Prevent DeprecationWarning about internal use of `asyncio.get_event_loop()` \ 
from affecting test cases

Log message:
py-test-asyncio: updated to 0.23.4

0.23.4 (2024-01-28)
===================
- pytest-asyncio no longer imports additional, unrelated packages during test \ 
collection
- Addresses further issues that caused an internal pytest error during test \ 
collection
- Declares incompatibility with pytest 8

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. 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.