Bumps [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) from 0.23.5 to 0.23.5.post1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pytest-dev/pytest-asyncio/releases">pytest-asyncio's releases</a>.</em></p> <blockquote> <h2>pytest-asyncio 0.23.5.post1</h2> <h1>0.23.5 (2024-02-09)</h1> <ul> <li>Declare compatibility with pytest 8 <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/737">#737</a></li> <li>Fix typing errors with recent versions of mypy <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/769">#769</a></li> <li>Prevent DeprecationWarning about internal use of <code>asyncio.get_event_loop()</code> from affecting test cases <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/757">#757</a></li> </ul> <h2>Known issues</h2> <p>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 <a href="https://redirect.github.com/pytest-dev/pytest-asyncio/issues/706">#706</a>). 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.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/b22d84e1f0d53920352be4c66d1b6c7f7a9ce005"><code>b22d84e</code></a> [docs] Fixes the example showing how to run all tests in a session-scoped loop.</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/f1de446a37b426f5882b103d5c2fd2f3045b1f01"><code>f1de446</code></a> Build(deps): Bump hypothesis in /dependencies/default</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/b60649a648912a79ce6f3443ca7ac2c67fe9a5b7"><code>b60649a</code></a> Build(deps): Bump urllib3 from 2.2.0 to 2.2.1 in /dependencies/docs</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/4baec47b8514b405e97a14a1d6c42fa07af8fb0a"><code>4baec47</code></a> Build(deps): Bump typing-extensions in /dependencies/default</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/d44e3ac013cb3b6736492d3f920fb8820f3c8bbf"><code>d44e3ac</code></a> Build(deps): Bump pytest from 8.0.0 to 8.0.2 in /dependencies/default</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/cefa62e7d007b5aa0add7bd58a3e33f246daee71"><code>cefa62e</code></a> Build(deps): Bump coverage from 7.4.1 to 7.4.3 in /dependencies/default</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/290886063f1da8ec1865cd2cdae721b0ebb89edf"><code>2908860</code></a> Build(deps): Bump hypothesis in /dependencies/default</li> <li><a href="https://github.com/pytest-dev/pytest-asyncio/commit/20bd7d87bec30ee49a2ec1adc8df8857fc0a69ac"><code>20bd7d8</code></a> Build(deps): Bump pypa/gh-action-pypi-publish from 1.8.11 to 1.8.12</li> <li>See full diff in <a href="https://github.com/pytest-dev/pytest-asyncio/compare/v0.23.5...v0.23.5.post1">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pytest-asyncio&package-manager=pip&previous-version=0.23.5&new-version=0.23.5.post1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>