…vent loop when a module has the mark.

Signed-off-by: Michael Seifert <m.seifert@digitalernachschub.de>

…nt loop implementation to pollute the test environment.

Signed-off-by: Michael Seifert <m.seifert@digitalernachschub.de>

…event loop implementation from polluting the test environment.

Signed-off-by: Michael Seifert <m.seifert@digitalernachschub.de>

…tor tests no longer requires an explicit event loop argument.

The wrapper retrieves the currently set loop via asyncio.get_event_loop, instead.

Signed-off-by: Michael Seifert <m.seifert@digitalernachschub.de>

…the function-scoped event_loop fixture.

They rather provide a fixture with a different name, based on the nodeid of the pytest.Collector that has the "asyncio_event_loop" mark.

When a test requests the event_loop fixture and a dynamically generated event loop with class or module scope, pytest-asyncio will raise an error.

Signed-off-by: Michael Seifert <m.seifert@digitalernachschub.de>

…p inside the event_loop fixture override rather than on the module-level.

This prevents the custom loop from being created during test collection time.

Signed-off-by: Michael Seifert <m.seifert@digitalernachschub.de>

…policy.

Signed-off-by: Michael Seifert <m.seifert@digitalernachschub.de>

…sing an iterable of policies.

This causes tests under the _asyncio_event_loop_ mark to be parametrized with the different loop policies.

Signed-off-by: Michael Seifert <m.seifert@digitalernachschub.de>