Update dependency pytest-asyncio to v1 #16
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/pytest-asyncio-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
==0.26.0→==1.4.1Release Notes
pytest-dev/pytest-asyncio (pytest-asyncio)
v1.4.1: pytest-asyncio v1.4.1Compare Source
1.4.1 - 2026-10-25
Added
Fixed
Notes for Downstream Packagers
uv.lock. (#1518)v1.4.0: pytest-asyncio v1.4.0Compare Source
1.4.0 - 2026-05-26
Deprecated
pytest_asyncio_loop_factorieshook instead. (#1419)Added
Added the
pytest_asyncio_loop_factorieshook to parametrize asyncio tests with custom event loop factories.The hook returns a mapping of factory names to loop factories, and
pytest.mark.asyncio(loop_factories=[...])selects a subset of configured factories per test. When a single factory is configured, test names are unchanged.Synchronous
@pytest_asyncio.fixturefunctions now see the correct event loop when custom loop factories are configured, even when test code disrupts the current event loop (e.g., viaasyncio.run()orasyncio.set_event_loop(None)). (#1164)Changed
asyncio_default_fixture_loop_scopeis unset (#1298)asyncio.AbstractEventLoopPolicyfor type checking to avoid raisinga DeprecationWarning. (#1394)
Fixed
ResourceWarning: unclosed event loopwarning that could occur when a synchronous test calledasyncio.run()or otherwise unset the current event loop after pytest-asyncio had run an async test or fixture. (#724)Notes for Downstream Packagers
sphinx-tabs >= 3.5to organize documentation examples into tabs. (#1395)v1.3.0: pytest-asyncio 1.3.0Compare Source
1.3.0 - 2025-11-10
Removed
Added
Notes for Downstream Packagers
pytest.Pytester.runpytest_subprocess. This prevents the test suite from accidentally using a system installation of pytest-asyncio, which could result in test errors. (#1275)v1.2.0: pytest-asyncio 1.2.0Compare Source
1.2.0 - 2025-09-12
Added
--asyncio-debugCLI option andasyncio_debugconfiguration option to enable asyncio debug mode for the default event loop. (#980)pytest.UsageErrorfor invalid configuration values ofasyncio_default_fixture_loop_scopeandasyncio_default_test_loop_scope. (#1189)Fixed
RuntimeError: There is no current event loop in thread 'MainThread'when any test unsets the event loop (such as when usingasyncio.runandasyncio.Runner). (#1177)@pytest.fixturein [strict]{.title-ref} mode. The warning message now refers to the correct package. (#1198)Notes for Downstream Packagers
tox.inifile provided by pytest-asyncio to run tests.v1.1.1: pytest-asyncio 1.1.1Compare Source
v1.1.1 - 2025-09-12
Notes for Downstream Packagers
- Addresses a build problem with setuptoos-scm >= 9 caused by invalid setuptools-scm configuration in pytest-asyncio. (#1192)
v1.1.0: pytest-asyncio 1.1.0Compare Source
Added
loop_scopeends (#200)Fixed
finallyclause of a task (#878)Notes for Downstream Packagers
v1.0.0: pytest-asyncio 1.0.0Compare Source
1.0.0 - 2025-05-26
Removed
(#1106)
Added
(#1025)
Changed
than per scope (e.g. per module). This reduces the number of fixtures
and speeds up collection time, especially for large test suites.
(#1107)
pytest.mark.asynciono longer forcesthat a pytest Collector exists at the level of the specified scope.
For example, a test function marked with
pytest.mark.asyncio(loop_scope="class")no longer requires a classsurrounding the test. This is consistent with the behavior of the
scope argument to
pytest_asyncio.fixture.(#1112)
Fixed
option.
(#630)
--doctest-ignore-import-errors(#797)
(#1052)
Notes for Downstream Packagers
(#1114)
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.
Pull request closed