Pytest-asyncio

Latest version: v0.24.0

Safety actively analyzes 685838 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 10

0.23.5.post1

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

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

0.23.4a1

Page 2 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.