Bump pytest-asyncio from 0.21.1 to 0.23.2

[dependabot]

Bumps pytest-asyncio from 0.21.1 to 0.23.2.

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 0.23.2

0.23.2 (2023-12-04)

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

pytest-asyncio 0.23.1

0.23.1 (2023-12-03)

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

pytest-asyncio 0.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 #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

pytest-asyncio 0.23.0b0

0.23.0 (UNRELEASED)

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
• Removes pytest-trio from the test dependencies #620

pytest-asyncio 0.23.0a1

0.23.0 (UNRELEASED)

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
• Removes pytest-trio from the test dependencies #620

pytest-asyncio 0.23.0a0

0.23.0 (UNRELEASED)

This release is backwards-compatible with v0.21. Changes are non-breaking, unless you upgrade from v0.22.

... (truncated)

Commits

• b614c77 [fix] Fixes a bug that caused an internal pytest error when collecting .txt f...
• a214c3e [fix] Fixes a bug that caused an internal pytest error when using module-leve...
• 176d558 [refactor] Extracted test for pytest.skip into a separate test module.
• 0b34e8e [chore] Prepare release of v0.23.0
• 3c2691d [docs] Remove badge which points out that the project uses Black as a code fo...
• 349c152 [docs] Mention the #pytest-asyncio:matrix.org chat room in README and for get...
• 533b886 Build(deps): Bump hypothesis in /dependencies/default
• 9a8b431 Build(deps): Bump exceptiongroup in /dependencies/default
• 540426d Build(deps): Bump pygments from 2.17.1 to 2.17.2 in /dependencies/docs
• ee23a65 Build(deps): Bump idna from 3.4 to 3.6 in /dependencies/docs
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[Bibo-Joshi]

There seem to be some systematic changes causing the event loop to be closed on every other test. Haven't investiged yet.

[harshil21]

oops, that's unreleased. Guess we can wait.

[dependabot]

A newer version of pytest-asyncio exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

[harshil21]

From the release notes:

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 pytest-dev/pytest-asyncio#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.

I suppose we have to wait for v0.24. I vote to close this PR then.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.