Update dependency pytest-asyncio to v0.23.3 #50

Merged
Renovate merged 1 commits from renovate/pytest-asyncio-0.x into dev 2024-01-01 18:09:27 +02:00
Collaborator

This PR contains the following updates:

Package Update Change
pytest-asyncio (changelog) patch ==0.23.2 -> ==0.23.3

Release Notes

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

v0.23.3: pytest-asyncio 0.23.3

Compare Source

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
  • Fixes various bugs that caused an internal pytest error during test collection #​711 #​713 #​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). 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 - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 Renovate Bot.

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/latest/reference/changelog.html)) | patch | `==0.23.2` -> `==0.23.3` | --- ### Release Notes <details> <summary>pytest-dev/pytest-asyncio (pytest-asyncio)</summary> ### [`v0.23.3`](https://github.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.3): pytest-asyncio 0.23.3 [Compare Source](https://github.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 [#&#8203;706](https://github.com/pytest-dev/pytest-asyncio/issues/706) - Fixes various bugs that caused an internal pytest error during test collection [#&#8203;711](https://github.com/pytest-dev/pytest-asyncio/issues/711) [#&#8203;713](https://github.com/pytest-dev/pytest-asyncio/issues/713) [#&#8203;719](https://github.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 [#&#8203;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. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **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 [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNi4zNS4wIiwidXBkYXRlZEluVmVyIjoiMzYuMzUuMCIsInRhcmdldEJyYW5jaCI6ImRldiJ9-->
Renovate added 1 commit 2024-01-01 17:06:10 +02:00
Update dependency pytest-asyncio to v0.23.3
All checks were successful
Tests / test (3.10) (pull_request) Successful in 1m13s
Tests / test (3.11) (pull_request) Successful in 1m13s
Tests / test (3.8) (pull_request) Successful in 1m15s
Tests / test (3.9) (pull_request) Successful in 1m13s
a0538625e2
Renovate merged commit a0538625e2 into dev 2024-01-01 18:09:27 +02:00
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
1 Participants
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: profitroll/LibBotUniversal#50
No description provided.