tests: add pytest.ini to set asyncio_default_fixture_loop_scope #115
+2
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Recent versions of pytest-asyncio and pytest introduced stricter handling of asynchronous fixtures. If the 'asyncio_default_fixture_loop_scope' option is unset, async fixtures may emit DeprecationWarnings during pytest configuration. This can break tests using pytester by preventing pytest from generating a terminal summary. This prevents the warning and ensures consistent and stable test execution for async tests. Signed-off-by: Maxim Tulskiy <[email protected]>
Max-Tulskiy
force-pushed
the
fix/pytest-asyncio-default-loop-scope
branch
from
2d6e4d3 to
26b8c8c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What do these changes do?
Adds pytest.ini to set 'asyncio_default_fixture_loop_scope = function'
to prevent pytest-asyncio deprecation warnings breaking pytester tests.
Are there changes in behavior for the user?
None; only affects test runs.
Checklist