Update dependency pytest-asyncio to v0.23.6 - autoclosed #12

Closed

Renovate wants to merge 1 commits from renovate/pytest-asyncio-0.x into dev

pull from: renovate/pytest-asyncio-0.x

merge into: profitroll:dev

profitroll:master

profitroll:dev

Conversation 0 Commits 1 Files Changed 1 +1 -1

Renovate commented 2024-03-26 17:35:38 +02:00

Collaborator

Copy Link

This PR contains the following updates:

Package	Update	Change
pytest-asyncio (changelog)	minor	==0.22.0 -> ==0.23.6

---

Release Notes

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

v0.23.6: pytest-asyncio 0.23.6

Compare Source

0.23.6 (2024-03-19)

• Fix compatibility with pytest 8.2 #​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). 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: pytest-asyncio 0.23.5.post1

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

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.

v0.23.2: pytest-asyncio 0.23.2

Compare Source

0.23.2 (2023-12-04)

• Fixes a bug that caused an internal pytest error when collecting .txt files #​703

v0.23.1: pytest-asyncio 0.23.1

Compare Source

0.23.1 (2023-12-03)

• Fixes a bug that caused an internal pytest error when using module-level skips #​701

v0.23.0: pytest-asyncio 0.23.0

Compare Source

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
• Introduces pytest_asyncio.is_async_test which returns whether a
  test item is managed by pytest-asyncio #​376
• Removes and pytest-trio, mypy, and flaky from the test
  dependencies #​620, #​674, #​678

---

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)) | minor | `==0.22.0` -> `==0.23.6` | --- ### Release Notes <details> <summary>pytest-dev/pytest-asyncio (pytest-asyncio)</summary> ### [`v0.23.6`](https://github.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.6): pytest-asyncio 0.23.6 [Compare Source](https://github.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 [#&#8203;800](https://github.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 [#&#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.5.post1`](https://github.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.5.post1): pytest-asyncio 0.23.5.post1 [Compare Source](https://github.com/pytest-dev/pytest-asyncio/compare/v0.23.5...v0.23.5.post1) ### 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.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) ### [`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. ### [`v0.23.2`](https://github.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.2): pytest-asyncio 0.23.2 [Compare Source](https://github.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 [#&#8203;703](https://github.com/pytest-dev/pytest-asyncio/issues/703) ### [`v0.23.1`](https://github.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.1): pytest-asyncio 0.23.1 [Compare Source](https://github.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 [#&#8203;701](https://github.com/pytest-dev/pytest-asyncio/issues/701) ### [`v0.23.0`](https://github.com/pytest-dev/pytest-asyncio/releases/tag/v0.23.0): pytest-asyncio 0.23.0 [Compare Source](https://github.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 [#&#8203;662](https://github.com/pytest-dev/pytest-asyncio/pull/662) - Introduces `pytest_asyncio.is_async_test` which returns whether a test item is managed by pytest-asyncio [#&#8203;376](https://github.com/pytest-dev/pytest-asyncio/issues/376) - Removes and *pytest-trio,* *mypy,* and *flaky* from the test dependencies [#&#8203;620](https://github.com/pytest-dev/pytest-asyncio/pull/620), [#&#8203;674](https://github.com/pytest-dev/pytest-asyncio/pull/674), [#&#8203;678](https://github.com/pytest-dev/pytest-asyncio/pull/678) </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-03-26 17:35:39 +02:00

Update dependency pytest-asyncio to v0.23.6 d83b8b54f9

Renovate scheduled this pull request to auto merge when all checks succeed 2024-03-26 17:35:39 +02:00

Renovate force-pushed renovate/pytest-asyncio-0.x from d83b8b54f9 to ab0952aea4 2024-03-27 12:23:00 +02:00 Compare

Renovate changed title from Update dependency pytest-asyncio to v0.23.6 to Update dependency pytest-asyncio to v0.23.6 - autoclosed 2024-03-27 12:28:17 +02:00

Renovate closed this pull request 2024-03-27 12:28:17 +02:00

Some checks failed

Hide all checks

Tests / test (3.10) (pull_request) Failing after 23m10s

Details

Tests / test (3.11) (pull_request) Failing after 23m24s

Details

Tests / test (3.8) (pull_request) Failing after 23m10s

Details

Tests / test (3.9) (pull_request) Failing after 23m10s

Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

Kind/Breaking

Breaking change that won't be backward compatible

  

Kind/Bug

Something is not working

  

Kind/Documentation

Documentation changes

  

Kind/Enhancement

Improve existing functionality

  

Kind/Feature

New functionality

  

Kind/Security

This is security issue

  

Kind/Testing

Issue or pull request related to testing

  

Priority

Critical

The priority is critical

  

Priority

High

The priority is high

  

Priority

Low

The priority is low

  

Priority

Medium

The priority is medium

  

Reviewed

Confirmed

Issue has been confirmed

  

Reviewed

Duplicate

This issue or pull request already exists

  

Reviewed

Invalid

Invalid issue

  

Reviewed

Won't Fix

This issue won't be fixed

  

Status

Abandoned

Somebody has started to work on this but abandoned work

  

Status

Blocked

Something is blocking this issue or pull request

  

Status

Need More Info

Feedback is required to reproduce issue or to continue work

No Label

Kind/Breaking

Kind/Bug

Kind/Documentation

Kind/Enhancement

Kind/Feature

Kind/Security

Kind/Testing

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Reviewed

Confirmed

Reviewed

Duplicate

Reviewed

Invalid

Reviewed

Won't Fix

Status

Abandoned

Status

Blocked

Status

Need More Info

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

1 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: profitroll/PythonRMV#12

No description provided.