Sourced frompytest-asyncio's releases.

pytest-asyncio 0.25.0

0.25.0 (2024-12-13)

• Deprecated: Added warning when asyncio test requests async@pytest.fixture in strict mode. This will become an error in a future version of flake8-asyncio.#979
• Updates the error message aboutpytest.mark.asyncio'sscope keyword argument to sayloop_scope instead.#1004
• Verbose log displays correct parameter name: asyncio_default_fixture_loop_scope#990
• Propagatescontextvars set in async fixtures to other fixtures and tests on Python 3.11 and above.#1008

pytest-asyncio 0.24.0

0.24.0 (2024-08-22)

• BREAKING: Updated minimum supported pytest version to v8.2.0
• Adds an optionalloop_scope keyword argument topytest.mark.asyncio. This argument controls which event loop is used to run the marked async test.#706,#871
• Deprecates the optionalscope keyword argument topytest.mark.asyncio for API consistency withpytest_asyncio.fixture. Users are encouraged to use theloop_scope keyword argument, which does exactly the same.
• Raises an error when passingscope orloop_scope as a positional argument to@pytest.mark.asyncio.#812
• Fixes a bug that caused module-scoped async fixtures to fail when reused in other modules#862#668

pytest-asyncio 0.24.0a1

0.24.0 (UNRELEASED)

• BREAKING: Updated minimum supported pytest version to v8.2.0
• Adds an optionalloop_scope keyword argument topytest.mark.asyncio. This argument controls which event loop is used to run the marked async test.#706,#871
• Deprecates the optionalscope keyword argument topytest.mark.asyncio for API consistency withpytest_asyncio.fixture. Users are encouraged to use theloop_scope keyword argument, which does exactly the same.
• Raises an error when passingscope orloop_scope as a positional argument to@pytest.mark.asyncio.#812
• Fixes a bug that caused module-scoped async fixtures to fail when reused in other modules#862#668

pytest-asyncio 0.24.0a0

0.24.0 (UNRELEASED)

• Adds an optionalloop_scope keyword argument topytest.mark.asyncio. This argument controls which event loop is used to run the marked async test.#706,#871
• Deprecates the optionalscope keyword argument topytest.mark.asyncio for API consistency withpytest_asyncio.fixture. Users are encouraged to use theloop_scope keyword argument, which does exactly the same.
• Raises an error when passingscope orloop_scope as a positional argument to@pytest.mark.asyncio.#812

pytest-asyncio 0.23.8

0.23.8 (2024-07-17)

• Fixes a bug that caused duplicate markers in async tests#813

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

... (truncated)

• b24de08 build: Prepare release of v0.25.0
• 9fd64da changelog +=asyncio_default_fixture_loop_scope
• f15b9c2 Add release note for#1008
• 0184cba Refactor tests to use Pytester
• 97c682f Copy context variables from non-generator fixtures
• 62ab185 Improve contextvars test coverage
• 3004bb7 Simplify contextvars support
• 746c114 Maintain contextvars.Context in fixtures and tests
• ebbd602 docs: describe when UsageError is raised for loop_scope="class" marker
• c4c1b48 Build(deps): Bump hypothesis in /dependencies/default
• Additional commits viewable incompare view

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)