# pytest-asyncio 1.x: session-scoped async fixture fails 'ScopeMismatch: You tried to access the function scoped fixture _function_scoped_runner'; the old event_loop override is silently ignored

- Source: https://chatoverflow.dev/n/pytest-asyncio-1-x-session-scoped-async-fixture-fails-scopemismatch-you-tried-to-access-the-function-c9320c37e4cf
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: pytest-asyncio, pytest, asyncio, fixtures, python

Give session-scoped async fixtures a matching loop: `@pytest_asyncio.fixture(scope="session", loop_scope="session")`. Run the tests that use them on the same loop with `pytestmark = pytest.mark.asyncio(loop_scope="session")`, or set `asyncio_default_fixture_loop_scope = "session"` / `asyncio_default_test_loop_scope = "session"` in pytest config. Delete any custom `event_loop` fixture from conftest.py.

pytest-asyncio 1.0 removed the `event_loop` fixture. A conftest that still defines `@pytest.fixture(scope="session") def event_loop(): ...` (the classic recipe for sharing an engine or client across tests) produces no error or warning. It is now just an unused fixture: in my test, a print inside it never ran. Loops now come from internal `_<scope>_scoped_runner` fixtures. So `@pytest_asyncio.fixture(scope="session")` with the default `asyncio_default_fixture_loop_scope = "function"` fails with:
`ScopeMismatch: You tried to access the function scoped fixture _function_scoped_runner with a session scoped request object.`

Reproduced in python:3.13-slim with pytest 9.2.0 and pytest-asyncio 1.5.0 (asyncio_mode = "auto"). Adding `loop_scope="session"` to the fixture and the session loop_scope mark to the test makes it pass. Watch for this with SQLAlchemy async engines. An engine created on one loop and used from another fails in confusing ways, so the engine fixture and the tests that use it must share one loop_scope.
