Update dependency pytest-asyncio to v1.4.0 #63

Merged
tux merged 1 commit from renovate/pytest-asyncio-1.x into main 2026-05-26 13:28:45 +02:00
Collaborator

This PR contains the following updates:

Package Update Change
pytest-asyncio (changelog) minor ==1.3.0==1.4.0

Release Notes

pytest-dev/pytest-asyncio (pytest-asyncio)

v1.4.0: pytest-asyncio v1.4.0

Compare Source

1.4.0 - 2026-05-26

Deprecated

  • Overriding the event_loop_policy fixture is deprecated. Use the pytest_asyncio_loop_factories hook instead. (#​1419)

Added

  • Added the pytest_asyncio_loop_factories hook to parametrize asyncio tests with custom event loop factories.

    The hook returns a mapping of factory names to loop factories, and pytest.mark.asyncio(loop_factories=[...]) selects a subset of configured factories per test. When a single factory is configured, test names are unchanged.

    Synchronous @pytest_asyncio.fixture functions now see the correct event loop when custom loop factories are configured, even when test code disrupts the current event loop (e.g., via asyncio.run() or asyncio.set_event_loop(None)). (#​1164)

Changed

  • Improved the readability of the warning message that is displayed when asyncio_default_fixture_loop_scope is unset (#​1298)
  • Only import asyncio.AbstractEventLoopPolicy for type checking to avoid raising
    a DeprecationWarning. (#​1394)
  • Updated minimum supported pytest version to v8.4.0. (#​1397)

Fixed

  • Fixed a ResourceWarning: unclosed event loop warning that could occur when a synchronous test called asyncio.run() or otherwise unset the current event loop after pytest-asyncio had run an async test or fixture. (#​724)

Notes for Downstream Packagers

  • Added dependency on sphinx-tabs >= 3.5 to organize documentation examples into tabs. (#​1395)

Configuration

📅 Schedule: (UTC)

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


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) ([changelog](https://pytest-asyncio.readthedocs.io/en/stable/reference/changelog.html)) | minor | `==1.3.0` → `==1.4.0` | --- ### Release Notes <details> <summary>pytest-dev/pytest-asyncio (pytest-asyncio)</summary> ### [`v1.4.0`](https://github.com/pytest-dev/pytest-asyncio/releases/tag/v1.4.0): pytest-asyncio v1.4.0 [Compare Source](https://github.com/pytest-dev/pytest-asyncio/compare/v1.3.0...v1.4.0) ### [1.4.0](https://github.com/pytest-dev/pytest-asyncio/tree/1.4.0) - 2026-05-26 #### Deprecated - Overriding the *event\_loop\_policy* fixture is deprecated. Use the `pytest_asyncio_loop_factories` hook instead. ([#&#8203;1419](https://github.com/pytest-dev/pytest-asyncio/issues/1419)) #### Added - Added the `pytest_asyncio_loop_factories` hook to parametrize asyncio tests with custom event loop factories. The hook returns a mapping of factory names to loop factories, and `pytest.mark.asyncio(loop_factories=[...])` selects a subset of configured factories per test. When a single factory is configured, test names are unchanged. Synchronous `@pytest_asyncio.fixture` functions now see the correct event loop when custom loop factories are configured, even when test code disrupts the current event loop (e.g., via `asyncio.run()` or `asyncio.set_event_loop(None)`). ([#&#8203;1164](https://github.com/pytest-dev/pytest-asyncio/issues/1164)) #### Changed - Improved the readability of the warning message that is displayed when `asyncio_default_fixture_loop_scope` is unset ([#&#8203;1298](https://github.com/pytest-dev/pytest-asyncio/issues/1298)) - Only import `asyncio.AbstractEventLoopPolicy` for type checking to avoid raising a DeprecationWarning. ([#&#8203;1394](https://github.com/pytest-dev/pytest-asyncio/issues/1394)) - Updated minimum supported pytest version to v8.4.0. ([#&#8203;1397](https://github.com/pytest-dev/pytest-asyncio/issues/1397)) #### Fixed - Fixed a `ResourceWarning: unclosed event loop` warning that could occur when a synchronous test called `asyncio.run()` or otherwise unset the current event loop after pytest-asyncio had run an async test or fixture. ([#&#8203;724](https://github.com/pytest-dev/pytest-asyncio/issues/724)) #### Notes for Downstream Packagers - Added dependency on `sphinx-tabs >= 3.5` to organize documentation examples into tabs. ([#&#8203;1395](https://github.com/pytest-dev/pytest-asyncio/issues/1395)) </details> --- ### Configuration 📅 **Schedule**: (UTC) - 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xNjAuNCIsInVwZGF0ZWRJblZlciI6IjQzLjE2MC40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
Update dependency pytest-asyncio to v1.4.0
All checks were successful
PyTest / build (pull_request) Successful in 1m18s
3f4dc0c14f
tux self-assigned this 2026-05-26 13:19:13 +02:00
tux merged commit f45ccc700d into main 2026-05-26 13:28:45 +02:00
tux deleted branch renovate/pytest-asyncio-1.x 2026-05-26 13:28:45 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Netz39_Vorstand/entities_validation_svc!63
No description provided.