Update pytest-asyncio to 0.25.1

[pyup-bot]

This PR updates pytest-asyncio from 0.23.2 to 0.25.1.

Changelog

0.25.1

- Fixes an issue that caused a broken event loop when a function-scoped test was executed in between two tests with wider loop scope [950](https://github.com/pytest-dev/pytest-asyncio/issues/950)
- Improves test collection speed in auto mode [1020](https://github.com/pytest-dev/pytest-asyncio/pull/1020)
- Corrects the warning that is emitted upon redefining the event_loop fixture

0.25.0

- 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. [979](https://github.com/pytest-dev/pytest-asyncio/pull/979)
- Updates the error message about _pytest.mark.asyncio_'s _scope_ keyword argument to say _loop_scope_ instead. [1004](https://github.com/pytest-dev/pytest-asyncio/pull/1004)
- Verbose log displays correct parameter name: asyncio_default_fixture_loop_scope [990](https://github.com/pytest-dev/pytest-asyncio/pull/990)
- Propagates _contextvars_ set in async fixtures to other fixtures and tests on Python 3.11 and above. [1008](https://github.com/pytest-dev/pytest-asyncio/pull/1008)

0.24.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. [706](https://github.com/pytest-dev/pytest-asyncio/issues/706), [#871](https://github.com/pytest-dev/pytest-asyncio/issues/871)
- 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``. [812](https://github.com/pytest-dev/pytest-asyncio/issues/812)

0.23.8

- Fixes a bug that caused duplicate markers in async tests [813](https://github.com/pytest-dev/pytest-asyncio/issues/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](https://github.com/pytest-dev/pytest-asyncio/issues/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.7

- Silence deprecation warnings about unclosed event loops that occurred with certain CPython patch releases [817](https://github.com/pytest-dev/pytest-asyncio/pull/817)

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](https://github.com/pytest-dev/pytest-asyncio/issues/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.6

- Fix compatibility with pytest 8.2 [800](https://github.com/pytest-dev/pytest-asyncio/pull/800)

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](https://github.com/pytest-dev/pytest-asyncio/issues/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.5

- Declare compatibility with pytest 8 [737](https://github.com/pytest-dev/pytest-asyncio/issues/737)
- Fix typing errors with recent versions of mypy [769](https://github.com/pytest-dev/pytest-asyncio/issues/769)

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](https://github.com/pytest-dev/pytest-asyncio/issues/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.4

- pytest-asyncio no longer imports additional, unrelated packages during test collection [729](https://github.com/pytest-dev/pytest-asyncio/issues/729)

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](https://github.com/pytest-dev/pytest-asyncio/issues/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.3

- 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 [708](https://github.com/pytest-dev/pytest-asyncio/issues/708)
- Fixes a bug that caused an internal pytest error when using unittest.SkipTest in a module [711](https://github.com/pytest-dev/pytest-asyncio/issues/711)

Links

• PyPI: https://pypi.org/project/pytest-asyncio
• Changelog: https://data.safetycli.com/changelogs/pytest-asyncio/