Don't warn about `asyncio_default_fixture_loop_scope` unless the test suite uses `pytest-asyncio`

[Liam-DeVoe]

Hi all. I am not a user of pytest-asyncio, but it has gotten installed to my environment through one transitive dependency or another.

My test suite has no async tests and runs under -Werror. One of my tests uses pytester.runpytest_inprocess, which fails iff pytest-asyncio is installed due to the deprecation warning:

INTERNALERROR>   File "/Users/tybug/.local/share/uv/python/cpython-3.13.11-macos-aarch64-none/lib/python3.13/site-packages/pytest_asyncio/plugin.py", line 247, in pytest_configure
INTERNALERROR>     warnings.warn(PytestDeprecationWarning(_DEFAULT_FIXTURE_LOOP_SCOPE_UNSET))
INTERNALERROR>     ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
INTERNALERROR> pytest.PytestDeprecationWarning: The configuration option "asyncio_default_fixture_loop_scope" is unset.
INTERNALERROR> The event loop scope for asynchronous fixtures will default to the fixture caching scope. Future versions of pytest-asyncio will default the loop scope for asynchronous fixtures to function scope. Set the default fixture loop scope explicitly in order to avoid unexpected behavior in the future. Valid fixture loop scopes are: "function", "class", "module", "package", "session"
================================================================= short test summary info ==================================================================
FAILED test_a.py::test_a - assert <ExitCode.INTERNAL_ERROR: 3> == 0
==================================================================== 1 failed in 0.06s =====================================================================
 ~/Desktop/pytest_inprocess_repro λ 

Reproduction steps:

mkdir pytest_asyncio_repro && cd pytest_asyncio_repro
uv venv .venv --python 3.12
uv pip install --python .venv/bin/python pytest pytest-asyncio

# test_a.py
pytest_plugins = ["pytester"]

def test_a(pytester):
    pytester.makepyfile(test_inner="""
def test_b(): pass
""")
    result = pytester.runpytest_inprocess()
    assert result.ret == 0

• .venv/bin/python -m pytest test_a.py: passes
• .venv/bin/python -m pytest test_a.py -Werror: fails

I'm not asking for the deprecation warning to be removed or relaxed. But it would be really great if having pytest-asyncio installed in my environment didn't cause my tests to fail!

I also don't know why this requires pytester.runpytest_inprocess to trigger. I would expect this to be a problem when running pytest at the top level as well. This may be why nobody has complained about this yet.

[seifertm]

The warning is currently emitted by pytest-asyncio during pytest's configuration phase. Since all pytest plugins are enabled by default, you will see the warning as soon as you install pytest-asyncio in your environment.

It's probably possible to only emit the warning when a test actually uses pytest-asyncio. I agree that this is better than the current behavior. Pytest-asyncio already switched to strict mode by default to not break anyone's tests just by being installed. In this case, I'm not sure if it's worth the effort. I'd rather address the deprecation warning than spend time on it triggering only when a test uses pytest-asyncio.

As a workaround you can disable pytest-asyncio altogether by adding -p no:asyncio to your pytest call.

I assume that the warning triggers differently for Pytester.runpytest_inprocess and Pytester.runpytest_subprocess, because the packages on PYTHONPATH, and therefore the installed pytest plugins are different.