codecov[bot]
commented
6 months ago Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 94.59%. Comparing base (
9da9f90) to head (73d1280). Report is 1 commits behind head on master.
Additional details and impacted files
```diff @@ Coverage Diff @@ ## master #578 +/- ## ======================================= Coverage 94.59% 94.59% ======================================= Files 9 9 Lines 870 870 Branches 133 133 ======================================= Hits 823 823 Misses 20 20 Partials 27 27 ```:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This PR contains the following updates:
0.23.6->0.24.0Release Notes
pytest-dev/pytest-asyncio (pytest-asyncio)
### [`v0.24.0`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.24.0): pytest-asyncio 0.24.0 [Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.23.8...v0.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. [#706](https://togithub.com/pytest-dev/pytest-asyncio/issues/706), [#871](https://togithub.com/pytest-dev/pytest-asyncio/pull/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://togithub.com/pytest-dev/pytest-asyncio/issues/812) - Fixes a bug that caused module-scoped async fixtures to fail when reused in other modules [#862](https://togithub.com/pytest-dev/pytest-asyncio/issues/862) [#668](https://togithub.com/pytest-dev/pytest-asyncio/issues/668) ### [`v0.23.8`](https://togithub.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.8): pytest-asyncio 0.23.8 [Compare Source](https://togithub.com/pytest-dev/pytest-asyncio/compare/v0.23.7...v0.23.8) ### 0.23.8 (2024-07-17) - Fixes a bug that caused duplicate markers in async tests [#813](https://togithub.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://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.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.Configuration
š Schedule: Branch creation - "before 4am" in timezone America/Chicago, Automerge - At any time (no schedule defined).
š¦ Automerge: Enabled.
ā» Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
š Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.