renovate[bot]
commented
4 months ago Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (==0.23.7). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.
This PR contains the following updates:
==0.21.2->==0.23.7Release Notes
pytest-dev/pytest-asyncio (pytest-asyncio)
### [`v0.23.7`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.7): pytest-asyncio 0.23.7 [Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.23.6...v0.23.7) ##### 0.23.7 (2024-05-19) - Silence deprecation warnings about unclosed event loops that occurred with certain CPython patch releases [#817](https://togithub.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://togithub.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. ### [`v0.23.6`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.6): pytest-asyncio 0.23.6 [Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.23.5.post1...v0.23.6) ### 0.23.6 (2024-03-19) - Fix compatibility with pytest 8.2 [#800](https://togithub.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://togithub.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. ### [`v0.23.5.post1`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.5.post1): pytest-asyncio 0.23.5.post1 [Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.23.5...v0.23.5.post1) ### 0.23.5 (2024-02-09) - Declare compatibility with pytest 8 [#737](https://togithub.com/pytest-dev/pytest-asyncio/issues/737) - Fix typing errors with recent versions of mypy [#769](https://togithub.com/pytest-dev/pytest-asyncio/issues/769) - Prevent DeprecationWarning about internal use of `asyncio.get_event_loop()` from affecting test cases [#757](https://togithub.com/pytest-dev/pytest-asyncio/issues/757) #### 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://togithub.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. ### [`v0.23.5`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.5): pytest-asyncio 0.23.5 [Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.23.4...v0.23.5) ### 0.23.5 (2024-02-09) - Declare compatibility with pytest 8 [#737](https://togithub.com/pytest-dev/pytest-asyncio/issues/737) - Fix typing errors with recent versions of mypy [#769](https://togithub.com/pytest-dev/pytest-asyncio/issues/769) - Prevent DeprecationWarning about internal use of `asyncio.get_event_loop()` from affecting test cases [#757](https://togithub.com/pytest-dev/pytest-asyncio/issues/757) #### 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://togithub.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. ### [`v0.23.4`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.4): pytest-asyncio 0.23.4 [Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.23.3...v0.23.4) ### 0.23.4 (2024-01-28) - pytest-asyncio no longer imports additional, unrelated packages during test collection [#729](https://togithub.com/pytest-dev/pytest-asyncio/issues/729) - Addresses further issues that caused an internal pytest error during test collection - Declares incompatibility with pytest 8 [#737](https://togithub.com/pytest-dev/pytest-asyncio/issues/737) ### [`v0.23.3`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.3): pytest-asyncio 0.23.3 [Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.23.2...v0.23.3) ### 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](https://togithub.com/pytest-dev/pytest-asyncio/issues/706) - Fixes various bugs that caused an internal pytest error during test collection [#711](https://togithub.com/pytest-dev/pytest-asyncio/issues/711) [#713](https://togithub.com/pytest-dev/pytest-asyncio/issues/713) [#719](https://togithub.com/pytest-dev/pytest-asyncio/issues/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](https://togithub.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. ### [`v0.23.2`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.2): pytest-asyncio 0.23.2 [Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.23.1...v0.23.2) ### 0.23.2 (2023-12-04) - Fixes a bug that caused an internal pytest error when collecting .txt files [#703](https://togithub.com/pytest-dev/pytest-asyncio/issues/703) ### [`v0.23.1`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.1): pytest-asyncio 0.23.1 [Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.23.0...v0.23.1) ### 0.23.1 (2023-12-03) - Fixes a bug that caused an internal pytest error when using module-level skips [#701](https://togithub.com/pytest-dev/pytest-asyncio/issues/701) ### [`v0.23.0`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.0): pytest-asyncio 0.23.0 [Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.22.0...v0.23.0) This release is backwards-compatible with v0.21. Changes are non-breaking, unless you upgrade from v0.22. - BREAKING: The *asyncio_event_loop* mark has been removed. Event loops with class, module, package, and session scopes can be requested via the *scope* keyword argument to the *asyncio* mark. - Introduces the *event_loop_policy* fixture which allows testing with non-default or multiple event loops [#662](https://togithub.com/pytest-dev/pytest-asyncio/pull/662) - Introduces `pytest_asyncio.is_async_test` which returns whether a test item is managed by pytest-asyncio [#376](https://togithub.com/pytest-dev/pytest-asyncio/issues/376) - Removes and *pytest-trio,* *mypy,* and *flaky* from the test dependencies [#620](https://togithub.com/pytest-dev/pytest-asyncio/pull/620), [#674](https://togithub.com/pytest-dev/pytest-asyncio/pull/674), [#678](https://togithub.com/pytest-dev/pytest-asyncio/pull/678) ### [`v0.22.0`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.22.0): pytest-asyncio 0.22.0 (yanked) [Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.21.2...v0.22.0) *This release deprecated event loop overrides, but didn't provide adequate replacement functionality for all relevant use cases. As such, the release was yanked from PyPI.* ### 0.22.0 (2023-10-31) - Class-scoped and module-scoped event loops can be requested via the *asyncio_event_loop* mark. [#620](https://togithub.com/pytest-dev/pytest-asyncio/pull/620) - Deprecate redefinition of the *event_loop* fixture. [#587](https://togithub.com/pytest-dev/pytest-asyncio/issues/531) Users requiring a class-scoped or module-scoped asyncio event loop for their tests should mark the corresponding class or module with *asyncio_event_loop*. - Test items based on asynchronous generators always exit with *xfail* status and emit a warning during the collection phase. This behavior is consistent with synchronous yield tests. [#642](https://togithub.com/pytest-dev/pytest-asyncio/issues/642) - Remove support for Python 3.7 - Declare support for Python 3.12Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.