Bump pytest-asyncio from 0.23.2 to 0.23.7

[dependabot[bot]]

Bumps pytest-asyncio from 0.23.2 to 0.23.7.

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 0.23.7

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.

pytest-asyncio 0.23.6

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.

pytest-asyncio 0.23.5.post1

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.

pytest-asyncio 0.23.5

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.

pytest-asyncio 0.23.5a0

0.23.5 (UNRELEASED)

• Declare compatibility with pytest 8 #737
• Fix typing errors with recent versions of mypy #769

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.

pytest-asyncio 0.23.4

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

... (truncated)

Commits

• eb63d5a docs: Prepared for release of v0.23.7.
• da04a7a Build(deps): Bump exceptiongroup in /dependencies/default
• 00c667a Build(deps): Bump pytest from 8.1.1 to 8.2.0 in /dependencies/default
• 3bd9cd8 [docs] Add changelog entry.
• 15544f0 Revert GitHub Actions and Tox changes.
• 6316b28 Deduplicate simplefilter snippet.
• 3ffdfc5 asyncio.run(port_afinalizer())
• 0107fd7 Remove extra space.
• 3bf700a Fix GH Action mapping.
• d15dc31 Fix 3109/3108 typo.
• 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 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)

[github-actions[bot]]

🦙 MegaLinter status: ❌ ERROR

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	3		0	0.02s
✅ BASH	bash-exec	1		0	0.0s
✅ BASH	shellcheck	1		0	0.02s
✅ BASH	shfmt	1	0	0	0.01s
✅ DOCKERFILE	hadolint	1		0	0.08s
✅ JSON	jsonlint	2		0	0.17s
✅ JSON	prettier	2	0	0	0.62s
✅ JSON	v8r	2		0	2.49s
⚠️ MARKDOWN	markdownlint	5	0	1	1.09s
❌ MARKDOWN	markdown-link-check	5		26	4.49s
✅ MARKDOWN	markdown-table-formatter	5	0	0	0.44s
❌ PYTHON	bandit	14		1	1.22s
✅ PYTHON	black	18	1	0	1.54s
✅ PYTHON	flake8	18		0	0.59s
✅ PYTHON	isort	18	1	0	0.35s
✅ PYTHON	pylint	18		0	14.19s
✅ PYTHON	ruff	18	1	0	0.02s
✅ REPOSITORY	gitleaks	yes		no	0.07s
✅ REPOSITORY	git_diff	yes		no	0.0s
❌ REPOSITORY	grype	yes		1	11.53s
✅ REPOSITORY	secretlint	yes		no	0.71s
❌ REPOSITORY	trivy	yes		1	8.6s
✅ REPOSITORY	trivy-sbom	yes		no	3.43s
✅ REPOSITORY	trufflehog	yes		no	3.21s
✅ SPELL	lychee	14		0	4.08s
✅ YAML	prettier	7	0	0	0.87s
✅ YAML	v8r	7		0	8.63s
✅ YAML	yamllint	7		0	0.21s

See detailed report in MegaLinter reports

_MegaLinter is graciously provided by _

[github-actions[bot]]

🦙 MegaLinter status: ❌ ERROR

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	3		0	0.03s
✅ BASH	bash-exec	1		0	0.02s
✅ BASH	shellcheck	1		0	0.06s
✅ BASH	shfmt	1	0	0	0.01s
✅ DOCKERFILE	hadolint	1		0	0.14s
✅ JSON	jsonlint	2		0	0.2s
✅ JSON	prettier	2	0	0	0.63s
✅ JSON	v8r	2		0	2.47s
⚠️ MARKDOWN	markdownlint	5	0	1	1.04s
❌ MARKDOWN	markdown-link-check	5		26	3.17s
✅ MARKDOWN	markdown-table-formatter	5	0	0	0.38s
❌ PYTHON	bandit	14		1	1.27s
✅ PYTHON	black	18	1	0	1.47s
✅ PYTHON	flake8	18		0	0.68s
✅ PYTHON	isort	18	1	0	0.33s
✅ PYTHON	pylint	18		0	13.63s
✅ PYTHON	ruff	18	1	0	0.02s
✅ REPOSITORY	gitleaks	yes		no	0.1s
✅ REPOSITORY	git_diff	yes		no	0.01s
❌ REPOSITORY	grype	yes		1	12.14s
✅ REPOSITORY	secretlint	yes		no	0.69s
❌ REPOSITORY	trivy	yes		1	9.46s
✅ REPOSITORY	trivy-sbom	yes		no	4.28s
✅ REPOSITORY	trufflehog	yes		no	3.06s
✅ SPELL	lychee	14		0	0.57s
✅ YAML	prettier	7	0	0	0.82s
✅ YAML	v8r	7		0	8.26s
✅ YAML	yamllint	7		0	0.33s

See detailed report in MegaLinter reports

_MegaLinter is graciously provided by _