chore(deps): update dependency pytest-asyncio to ^0.24.0 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pytest-asyncio (changelog)	^0.21.0 -> ^0.24.0

---

Release Notes

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

v0.24.0: pytest-asyncio 0.24.0

Compare Source

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, #​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
• Fixes a bug that caused module-scoped async fixtures to fail when reused in other modules #​862 #​668

v0.23.8: pytest-asyncio 0.23.8

Compare Source

0.23.8 (2024-07-17)

• Fixes a bug that caused duplicate markers in async tests #​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). 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: pytest-asyncio 0.23.7

Compare Source

0.23.7 (2024-05-19)

• Silence deprecation warnings about unclosed event loops that occurred with certain CPython patch releases #​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). 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.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: 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

v0.22.0: pytest-asyncio 0.22.0 (yanked)

Compare Source

This release deprecated event loop overrides, but didn't provide adequate replacement functionality for all relevant use cases. As such, the release was yanked from PyPI.

0.22.0 (2023-10-31)

• Class-scoped and module-scoped event loops can be requested
  via the asyncio_event_loop mark. #​620
• Deprecate redefinition of the event_loop fixture. #​587
  Users requiring a class-scoped or module-scoped asyncio event loop for their tests
  should mark the corresponding class or module with asyncio_event_loop.
• Test items based on asynchronous generators always exit with xfail status and emit a warning during the collection phase. This behavior is consistent with synchronous yield tests. #​642
• Remove support for Python 3.7
• Declare support for Python 3.12

v0.21.2: pytest-asyncio 0.21.2

Compare Source

0.21.2 (2024-04-29)

• Fix compatibility with pytest 8.2. Backport of #​800 to pytest-asyncio v0.21 for users who are unable to upgrade to a more recent version (see #​706

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock

Updating dependencies
Resolving dependencies...

Creating virtualenv upnpavcontrol-1mFnt8Va-py3.10 in /home/ubuntu/.cache/pypoetry/virtualenvs

The current project's Python requirement (>=3.7,<3.11) is not compatible with some of the required packages Python requirement:
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.7,<3.8
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.7,<3.8
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.7,<3.8
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.7,<3.8
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.7,<3.8
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.7,<3.8
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.7,<3.8
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.7,<3.8

Because no versions of pytest-asyncio match >0.23.0,<0.23.1 || >0.23.1,<0.23.2 || >0.23.2,<0.23.3 || >0.23.3,<0.23.4 || >0.23.4,<0.23.5 || >0.23.5,<0.23.5.post1 || >0.23.5.post1,<0.23.6 || >0.23.6,<0.24.0
 and pytest-asyncio (0.23.0) requires Python >=3.8, pytest-asyncio is forbidden.
And because pytest-asyncio (0.23.1) requires Python >=3.8
 and pytest-asyncio (0.23.2) requires Python >=3.8, pytest-asyncio is forbidden.
And because pytest-asyncio (0.23.3) requires Python >=3.8
 and pytest-asyncio (0.23.4) requires Python >=3.8, pytest-asyncio is forbidden.
And because pytest-asyncio (0.23.5) requires Python >=3.8
 and pytest-asyncio (0.23.5.post1) requires Python >=3.8, pytest-asyncio is forbidden.
So, because pytest-asyncio (0.23.6) requires Python >=3.8
 and upnpavcontrol depends on pytest-asyncio (^0.23.0), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<3.11"
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<3.11"
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<3.11"
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<3.11"
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<3.11"
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<3.11"
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<3.11"
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<3.11"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock

Updating dependencies
Resolving dependencies...

Creating virtualenv upnpavcontrol-1mFnt8Va-py3.10 in /home/ubuntu/.cache/pypoetry/virtualenvs

The current project's Python requirement (>=3.7,<3.11) is not compatible with some of the required packages Python requirement:
  - pytest-asyncio requires Python >=3.8, so it will not be satisfied for Python >=3.7,<3.8

Because no versions of pytest-asyncio match >0.24.0,<0.25.0
 and pytest-asyncio (0.24.0) requires Python >=3.8, pytest-asyncio is forbidden.
So, because upnpavcontrol depends on pytest-asyncio (^0.24.0), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For pytest-asyncio, a possible solution would be to set the `python` property to ">=3.8,<3.11"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers