Bump pytest-asyncio from 0.23.2 to 0.23.4

[dependabot[bot]]

Bumps pytest-asyncio from 0.23.2 to 0.23.4.

Release notes

Sourced from pytest-asyncio's releases.

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

pytest-asyncio 0.23.4a2

0.23.4 (UNRELEASED)

• pytest-asyncio no longer imports additional, unrelated packages during test collection #729
• Addresses further issues that caused an internal pytest error during test collection

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

0.23.4 (UNRELEASED)

• pytest-asyncio no longer imports additional, unrelated packages during test collection #729

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

0.23.4 (UNRELEASED)

• pytest-asyncio no longer imports additional, unrelated packages during test collection #729

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

pytest-asyncio 0.23.3a0

0.23.3 (UNRELEASED)

• 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 #708
• Fixes a bug that caused an internal pytest error when using unittest.SkipTest in a module #711

Commits

• b879130 [chore] Updated shed pre-commit hook to v2024.1.1.
• a309bc5 [docs] Prepare release of v0.23.4.
• c51c3e7 [docs] Mention compatibility issue with pytest 8.
• dd129e9 [fix] Fixes a bug that prevented tests from being collected from package when...
• 463ce98 [fix] Avoid trying to install scoped event loops for unknown test collector t...
• 256ef7d [fix] pytest-asyncio no longer uses virtual modules to install dynamic packag...
• 8ba9bd0 [fix] Make virtual modules compatible with Windows.
• df487d5 [ci] Shorten names of display OS in CI jobs.
• 9572f3e [tests] Fixed deprecated use of yield_fixture in test.
• ef619b9 [build] Run tests on Windows.
• 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: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	3		0	0.06s
✅ BASH	bash-exec	1		0	0.0s
✅ BASH	shellcheck	1		0	0.03s
✅ BASH	shfmt	1	0	0	0.01s
✅ DOCKERFILE	hadolint	1		0	0.11s
✅ JSON	eslint-plugin-jsonc	2	0	0	1.03s
✅ JSON	jsonlint	2		0	0.21s
✅ JSON	prettier	2	0	0	0.37s
✅ JSON	v8r	2		0	2.85s
✅ MARKDOWN	markdownlint	5	0	0	1.05s
✅ MARKDOWN	markdown-link-check	5		0	2.48s
✅ MARKDOWN	markdown-table-formatter	5	0	0	0.43s
✅ PYTHON	bandit	14		0	1.34s
✅ PYTHON	black	18	0	0	1.39s
✅ PYTHON	flake8	18		0	1.0s
✅ PYTHON	isort	18	0	0	0.4s
✅ PYTHON	pylint	18		0	16.83s
✅ PYTHON	ruff	18	0	0	0.03s
✅ REPOSITORY	gitleaks	yes		no	0.15s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	grype	yes		no	14.48s
✅ REPOSITORY	secretlint	yes		no	0.75s
✅ REPOSITORY	trivy	yes		no	7.36s
✅ REPOSITORY	trivy-sbom	yes		no	1.75s
✅ REPOSITORY	trufflehog	yes		no	7.46s
✅ SPELL	lychee	14		0	0.59s
✅ YAML	prettier	7	0	0	0.87s
✅ YAML	v8r	7		0	9.38s
✅ YAML	yamllint	7		0	0.33s

See detailed report in MegaLinter reports

_MegaLinter is graciously provided by _

[dependabot[bot]]

Superseded by #46.