Update dependency pytest-asyncio to v0.23.5 #59

Merged
Renovate merged 1 commits from renovate/pytest-asyncio-0.x into dev 2024-02-17 16:39:12 +02:00
Collaborator

This PR contains the following updates:

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

Release Notes

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

v0.23.5: pytest-asyncio 0.23.5

Compare Source

0.23.5 (2024-02-09)

  • Declare compatibility with pytest 8 #​737
  • Fix typing errors with recent versions of mypy #​769
  • Prevent DeprecationWarning about internal use of asyncio.get_event_loop() from affecting test cases #​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). 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: pytest-asyncio 0.23.4

Compare Source

0.23.4 (2024-01-28)

  • pytest-asyncio no longer imports additional, unrelated packages during test collection #​729
  • Addresses further issues that caused an internal pytest error during test collection
  • Declares incompatibility with pytest 8 #​737

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.3` -> `==0.23.5` | --- ### Release Notes <details> <summary>pytest-dev/pytest-asyncio (pytest-asyncio)</summary> ### [`v0.23.5`](https://github.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.5): pytest-asyncio 0.23.5 [Compare Source](https://github.com/pytest-dev/pytest-asyncio/compare/v0.23.4...v0.23.5) ### 0.23.5 (2024-02-09) - Declare compatibility with pytest 8 [#&#8203;737](https://github.com/pytest-dev/pytest-asyncio/issues/737) - Fix typing errors with recent versions of mypy [#&#8203;769](https://github.com/pytest-dev/pytest-asyncio/issues/769) - Prevent DeprecationWarning about internal use of `asyncio.get_event_loop()` from affecting test cases [#&#8203;757](https://github.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 [#&#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. ### [`v0.23.4`](https://github.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.4): pytest-asyncio 0.23.4 [Compare Source](https://github.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 [#&#8203;729](https://github.com/pytest-dev/pytest-asyncio/issues/729) - Addresses further issues that caused an internal pytest error during test collection - Declares incompatibility with pytest 8 [#&#8203;737](https://github.com/pytest-dev/pytest-asyncio/issues/737) </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-28 22:04:12 +02:00
Update dependency pytest-asyncio to v0.23.4
Some checks failed
Tests / test (3.10) (pull_request) Failing after 1m11s
Tests / test (3.11) (pull_request) Failing after 57s
Tests / test (3.8) (pull_request) Failing after 48s
Tests / test (3.9) (pull_request) Failing after 48s
1a9173b978
Renovate scheduled this pull request to auto merge when all checks succeed 2024-01-28 22:04:12 +02:00
Renovate force-pushed renovate/pytest-asyncio-0.x from 1a9173b978 to 28f03f77c6 2024-02-06 22:05:21 +02:00 Compare
Renovate changed title from Update dependency pytest-asyncio to v0.23.4 to Update dependency pytest-asyncio to v0.23.5 2024-02-09 19:04:12 +02:00
Renovate force-pushed renovate/pytest-asyncio-0.x from 28f03f77c6 to e43dea17ec 2024-02-09 19:04:12 +02:00 Compare
Renovate force-pushed renovate/pytest-asyncio-0.x from e43dea17ec to 70abfbdeb3 2024-02-17 14:32:19 +02:00 Compare
Renovate force-pushed renovate/pytest-asyncio-0.x from 70abfbdeb3 to 0408cd676f 2024-02-17 15:35:47 +02:00 Compare
Renovate merged commit 0408cd676f into dev 2024-02-17 16:39:12 +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#59
No description provided.