pytest-asyncio 1.2.0__tar.gz → 1.4.0__tar.gz

{pytest_asyncio-1.2.0 → pytest_asyncio-1.4.0}/PKG-INFO

@@ -1,12 +1,12 @@
 Metadata-Version: 2.4
 Name: pytest-asyncio
-Version: 1.2.0
+Version: 1.4.0
 Summary: Pytest support for asyncio
 Author-email: Tin Tvrtković <tinchester@gmail.com>
 Maintainer-email: Michael Seifert <m.seifert@digitalernachschub.de>
 License-Expression: Apache-2.0
 Project-URL: Bug Tracker, https://github.com/pytest-dev/pytest-asyncio/issues
-Project-URL: Changelog, https://pytest-asyncio.readthedocs.io/en/latest/reference/changelog.html
+Project-URL: Changelog, https://pytest-asyncio.readthedocs.io/en/stable/reference/changelog.html
 Project-URL: Documentation, https://pytest-asyncio.readthedocs.io
 Project-URL: Homepage, https://github.com/pytest-dev/pytest-asyncio
 Project-URL: Source Code, https://github.com/pytest-dev/pytest-asyncio
@@ -15,7 +15,6 @@ Classifier: Framework :: AsyncIO
 Classifier: Framework :: Pytest
 Classifier: Intended Audience :: Developers
 Classifier: Programming Language :: Python :: 3 :: Only
-Classifier: Programming Language :: Python :: 3.9
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
@@ -23,15 +22,16 @@ Classifier: Programming Language :: Python :: 3.13
 Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Software Development :: Testing
 Classifier: Typing :: Typed
-Requires-Python: >=3.9
+Requires-Python: >=3.10
 Description-Content-Type: text/x-rst
 License-File: LICENSE
 Requires-Dist: backports-asyncio-runner<2,>=1.1; python_version < "3.11"
-Requires-Dist: pytest<9,>=8.2
+Requires-Dist: pytest<10,>=8.4
 Requires-Dist: typing-extensions>=4.12; python_version < "3.13"
 Provides-Extra: docs
 Requires-Dist: sphinx>=5.3; extra == "docs"
 Requires-Dist: sphinx-rtd-theme>=1; extra == "docs"
+Requires-Dist: sphinx-tabs>=3.5; extra == "docs"
 Provides-Extra: testing
 Requires-Dist: coverage>=6.2; extra == "testing"
 Requires-Dist: hypothesis>=5.7.1; extra == "testing"
@@ -53,7 +53,7 @@ pytest-asyncio
     :alt: Matrix chat room: #pytest-asyncio
     :target: https://matrix.to/#/#pytest-asyncio:matrix.org
 
-`pytest-asyncio <https://pytest-asyncio.readthedocs.io/en/latest/>`_ is a `pytest <https://docs.pytest.org/en/latest/contents.html>`_ plugin. It facilitates testing of code that uses the `asyncio <https://docs.python.org/3/library/asyncio.html>`_ library.
+`pytest-asyncio <https://pytest-asyncio.readthedocs.io/en/stable/>`_ is a `pytest <https://docs.pytest.org/en/latest/contents.html>`_ plugin. It facilitates testing of code that uses the `asyncio <https://docs.python.org/3/library/asyncio.html>`_ library.
 
 Specifically, pytest-asyncio provides support for coroutines as test functions. This allows users to *await* code inside their tests. For example, the following code is executed as a test item by pytest:
 
@@ -64,7 +64,7 @@ Specifically, pytest-asyncio provides support for coroutines as test functions.
         res = await library.do_something()
         assert b"expected result" == res
 
-More details can be found in the `documentation <https://pytest-asyncio.readthedocs.io/en/latest/>`_.
+More details can be found in the `documentation <https://pytest-asyncio.readthedocs.io/en/stable/>`_.
 
 Note that test classes subclassing the standard `unittest <https://docs.python.org/3/library/unittest.html>`__ library are not supported. Users
 are advised to use `unittest.IsolatedAsyncioTestCase <https://docs.python.org/3/library/unittest.html#unittest.IsolatedAsyncioTestCase>`__

{pytest_asyncio-1.2.0 → pytest_asyncio-1.4.0}/README.rst

@@ -14,7 +14,7 @@ pytest-asyncio
     :alt: Matrix chat room: #pytest-asyncio
     :target: https://matrix.to/#/#pytest-asyncio:matrix.org
 
-`pytest-asyncio <https://pytest-asyncio.readthedocs.io/en/latest/>`_ is a `pytest <https://docs.pytest.org/en/latest/contents.html>`_ plugin. It facilitates testing of code that uses the `asyncio <https://docs.python.org/3/library/asyncio.html>`_ library.
+`pytest-asyncio <https://pytest-asyncio.readthedocs.io/en/stable/>`_ is a `pytest <https://docs.pytest.org/en/latest/contents.html>`_ plugin. It facilitates testing of code that uses the `asyncio <https://docs.python.org/3/library/asyncio.html>`_ library.
 
 Specifically, pytest-asyncio provides support for coroutines as test functions. This allows users to *await* code inside their tests. For example, the following code is executed as a test item by pytest:
 
@@ -25,7 +25,7 @@ Specifically, pytest-asyncio provides support for coroutines as test functions.
         res = await library.do_something()
         assert b"expected result" == res
 
-More details can be found in the `documentation <https://pytest-asyncio.readthedocs.io/en/latest/>`_.
+More details can be found in the `documentation <https://pytest-asyncio.readthedocs.io/en/stable/>`_.
 
 Note that test classes subclassing the standard `unittest <https://docs.python.org/3/library/unittest.html>`__ library are not supported. Users
 are advised to use `unittest.IsolatedAsyncioTestCase <https://docs.python.org/3/library/unittest.html#unittest.IsolatedAsyncioTestCase>`__

pytest_asyncio-1.4.0/constraints.txt

@@ -0,0 +1,67 @@
+alabaster==1.0.0
+annotated-types-0.7.0
+attrs==26.1.0
+babel==2.18.0
+backports.asyncio.runner==1.2.0
+backports.tarfile==1.2.0
+certifi==2026.4.22
+charset-normalizer==3.4.7
+check-wheel-contents==0.6.3
+cffi==2.0.0
+click==8.4.0
+coverage==7.14.0
+cryptography==48.0.0
+docutils==0.21.2
+exceptiongroup==1.3.1
+hypothesis==6.152.8
+iniconfig==2.3.0
+id==1.6.1
+idna==3.15
+imagesize==2.0.0
+importlib_metadata==9.0.0
+iniconfig==2.3.0
+jaraco.classes==3.4.0
+jaraco.context==6.1.2
+jaraco.functools==4.5.0
+jeepney==0.9.0
+Jinja2==3.1.6
+keyring==25.7.0
+markdown-it-py==4.2.0
+MarkupSafe==3.0.3
+mdurl==0.1.2
+more-itertools==11.0.2
+nh3==0.3.5
+packaging==26.2
+pluggy==1.6.0
+Pygments==2.20.0
+pycparser==3.0
+pydantic==2.13.4
+pydantic-core==2.46.4
+pytest==9.0.3
+readme-renderer==44.0
+requests==2.34.2
+requests-toolbelt==1.0.0
+rfc3986==2.0.0
+rich==15.0.0
+SecretStorage==3.5.0
+setuptools==82.0.1
+setuptools-scm==10.0.5
+snowballstemmer==3.0.1
+sortedcontainers==2.4.0
+Sphinx==8.1.3
+sphinx-tabs==3.5.0
+sphinx-rtd-theme==3.1.0
+sphinxcontrib-applehelp==2.0.0
+sphinxcontrib-devhelp==2.0.0
+sphinxcontrib-htmlhelp==2.1.0
+sphinxcontrib-jquery==4.1
+sphinxcontrib-jsmath==1.0.1
+sphinxcontrib-qthelp==2.0.0
+sphinxcontrib-serializinghtml==2.0.0
+tomli==2.4.1
+twine==6.2.0
+typing_extensions==4.15.0
+typing-inspection==0.4.2
+urllib3==2.7.0
+wheel-filename==1.4.2
+zipp==4.1.0

{pytest_asyncio-1.2.0 → pytest_asyncio-1.4.0}/dependencies/pytest-min/constraints.txt

@@ -14,7 +14,7 @@ packaging==23.2
 pluggy==1.5.0
 py==1.11.0
 Pygments==2.16.1
-pytest==8.2.0
+pytest==8.4.0
 requests==2.31.0
 sortedcontainers==2.4.0
 tomli==2.0.1

{pytest_asyncio-1.2.0 → pytest_asyncio-1.4.0}/dependencies/pytest-min/requirements.txt

@@ -1,3 +1,3 @@
 # Always adjust install_requires in setup.cfg and requirements.txt
 # when changing minimum version dependencies
-pytest[testing] == 8.2.0
+pytest[testing] == 8.4.0

{pytest_asyncio-1.2.0 → pytest_asyncio-1.4.0}/docs/concepts.rst

@@ -47,30 +47,50 @@ Assigning neighboring tests to different event loop scopes is discouraged as it
 Test discovery modes
 ====================
 
-Pytest-asyncio provides two modes for test discovery, *strict* and *auto*. This can be set through Pytest's ``--asyncio-mode`` command line flag, or through the configuration file:
+Pytest-asyncio provides two modes for test discovery, *strict* and *auto*.
+This can be set through Pytest's ``--asyncio-mode`` command line flag,
+or through the configuration file.
 
-.. code-block:: toml
+.. tabs::
 
-    [tool.pytest.ini_options]
-    asyncio_mode = "auto" # or "strict"
+   .. group-tab:: Strict mode
 
-Strict mode
------------
+      .. code-block:: toml
 
-In strict mode pytest-asyncio will only run tests that have the *asyncio* marker and will only evaluate async fixtures decorated with ``@pytest_asyncio.fixture``. Test functions and fixtures without these markers and decorators will not be handled by pytest-asyncio.
+         [tool.pytest.ini_options]
+         asyncio_mode = "strict"
 
-This mode is intended for projects that want so support multiple asynchronous programming libraries as it allows pytest-asyncio to coexist with other async testing plugins in the same codebase.
+      In strict mode pytest-asyncio will only run tests that have the *asyncio* marker
+      and will only evaluate async fixtures decorated with ``@pytest_asyncio.fixture``.
+      Test functions and fixtures without these markers and decorators will not be
+      handled by pytest-asyncio.
 
-Pytest automatically enables installed plugins. As a result pytest plugins need to coexist peacefully in their default configuration. This is why strict mode is the default mode.
+      This mode is intended for projects that want to support multiple asynchronous
+      programming libraries as it allows pytest-asyncio to coexist with other async
+      testing plugins in the same codebase.
 
-Auto mode
----------
+      Pytest automatically enables installed plugins. As a result pytest plugins
+      need to coexist peacefully in their default configuration. This is why strict
+      mode is the default mode.
 
-In *auto* mode pytest-asyncio automatically adds the *asyncio* marker to all asynchronous test functions. It will also take ownership of all async fixtures, regardless of whether they are decorated with ``@pytest.fixture`` or ``@pytest_asyncio.fixture``.
+   .. group-tab:: Auto mode
 
-This mode is intended for projects that use *asyncio* as their only asynchronous programming library. Auto mode makes for the simplest test and fixture configuration and is the recommended default.
+      .. code-block:: toml
 
-If you intend to support multiple asynchronous programming libraries, e.g. *asyncio* and *trio*, strict mode will be the preferred option.
+         [tool.pytest.ini_options]
+         asyncio_mode = "auto"
+
+      In *auto* mode pytest-asyncio automatically adds the *asyncio* marker to all
+      asynchronous test functions. It will also take ownership of all async fixtures,
+      regardless of whether they are decorated with ``@pytest.fixture`` or
+      ``@pytest_asyncio.fixture``.
+
+      This mode is intended for projects that use *asyncio* as their only asynchronous
+      programming library. Auto mode makes for the simplest test and fixture
+      configuration and is the recommended default.
+
+      If you intend to support multiple asynchronous programming libraries,
+      e.g. *asyncio* and *trio*, strict mode will be the preferred option.
 
 .. _concepts/concurrent_execution:
 

{pytest_asyncio-1.2.0 → pytest_asyncio-1.4.0}/docs/conf.py

@@ -16,7 +16,7 @@ release = importlib.metadata.version(project)
 # -- General configuration ---------------------------------------------------
 # https://www.sphinx-doc.org/en/master/usage/configuration.html#general-configuration
 
-extensions = []
+extensions = ["sphinx_tabs.tabs"]
 
 templates_path = ["_templates"]
 exclude_patterns = []

{pytest_asyncio-1.2.0 → pytest_asyncio-1.4.0}/docs/how-to-guides/change_default_fixture_loop.rst

@@ -3,22 +3,27 @@ How to change the default event loop scope of all fixtures
 ==========================================================
 The :ref:`configuration/asyncio_default_fixture_loop_scope` configuration option sets the default event loop scope for asynchronous fixtures. The following code snippets configure all fixtures to run in a session-scoped loop by default:
 
-.. code-block:: ini
-    :caption: pytest.ini
+.. tabs::
 
-    [pytest]
-    asyncio_default_fixture_loop_scope = session
+   .. tab:: pytest.ini
 
-.. code-block:: toml
-    :caption: pyproject.toml
+      .. code-block:: ini
 
-    [tool.pytest.ini_options]
-    asyncio_default_fixture_loop_scope = "session"
+         [pytest]
+         asyncio_default_fixture_loop_scope = session
 
-.. code-block:: ini
-    :caption: setup.cfg
+   .. tab:: pyproject.toml
 
-    [tool:pytest]
-    asyncio_default_fixture_loop_scope = session
+      .. code-block:: toml
+
+         [tool.pytest.ini_options]
+         asyncio_default_fixture_loop_scope = "session"
+
+   .. tab:: setup.cfg
+
+      .. code-block:: ini
+
+         [tool:pytest]
+         asyncio_default_fixture_loop_scope = session
 
 Please refer to :ref:`configuration/asyncio_default_fixture_loop_scope` for other valid scopes.

{pytest_asyncio-1.2.0 → pytest_asyncio-1.4.0}/docs/how-to-guides/change_default_test_loop.rst

@@ -3,22 +3,28 @@ How to change the default event loop scope of all tests
 =======================================================
 The :ref:`configuration/asyncio_default_test_loop_scope` configuration option sets the default event loop scope for asynchronous tests. The following code snippets configure all tests to run in a session-scoped loop by default:
 
-.. code-block:: ini
-    :caption: pytest.ini
+.. tabs::
 
-    [pytest]
-    asyncio_default_test_loop_scope = session
+   .. tab:: pytest.ini
 
-.. code-block:: toml
-    :caption: pyproject.toml
+      .. code-block:: ini
 
-    [tool.pytest.ini_options]
-    asyncio_default_test_loop_scope = "session"
+         [pytest]
+         asyncio_default_test_loop_scope = session
 
-.. code-block:: ini
-    :caption: setup.cfg
+   .. tab:: pyproject.toml
 
-    [tool:pytest]
-    asyncio_default_test_loop_scope = session
+      .. code-block:: toml
 
-Please refer to :ref:`configuration/asyncio_default_test_loop_scope` for other valid scopes.
+         [tool.pytest.ini_options]
+         asyncio_default_test_loop_scope = "session"
+
+   .. tab:: setup.cfg
+
+      .. code-block:: ini
+
+         [tool:pytest]
+         asyncio_default_test_loop_scope = session
+
+Please refer to :ref:`configuration/asyncio_default_test_loop_scope`
+for other valid scopes.

pytest_asyncio-1.4.0/docs/how-to-guides/configure_loop_factories_per_test/conftest.py

@@ -0,0 +1,18 @@
+import asyncio
+
+import pytest
+
+
+class CustomEventLoop(asyncio.SelectorEventLoop):
+    pass
+
+
+@pytest.fixture
+def requires_custom_loop():
+    pass
+
+
+def pytest_asyncio_loop_factories(config, item):
+    if "requires_custom_loop" in item.fixturenames:
+        return {"custom": CustomEventLoop}
+    return {"default": asyncio.new_event_loop}

pytest_asyncio-1.4.0/docs/how-to-guides/configure_loop_factories_per_test/test_extra_loop_factories.py

@@ -0,0 +1,11 @@
+import pytest
+
+
+@pytest.mark.asyncio
+async def test_runs_with_default_factory_only():
+    pass
+
+
+@pytest.mark.asyncio
+async def test_runs_with_custom_factory_only(requires_custom_loop):
+    pass

pytest_asyncio-1.4.0/docs/how-to-guides/configure_loop_factories_per_test.rst

@@ -0,0 +1,29 @@
+========================================================
+How to configure event loop factories from the test item
+========================================================
+
+``pytest_asyncio_loop_factories`` is called with the current pytest ``item``.
+Use that item to decide which named event loop factories are available for the test being collected.
+
+For example, a hook can inspect the test's fixtures and return a different factory mapping for tests that request a particular fixture.
+In ``conftest.py``, check the current item's fixture names and build the factory mapping for that item:
+
+.. include:: configure_loop_factories_per_test/conftest.py
+   :code: python
+
+Then request the fixture from tests that should use the custom factory:
+
+.. include:: configure_loop_factories_per_test/test_extra_loop_factories.py
+   :code: python
+
+In this example, ``test_runs_with_default_factory_only`` is parametrized only over ``default``, while ``test_runs_with_custom_factory_only`` is parametrized only over ``custom``.
+
+The same pattern works with any information available from the current pytest item, such as fixture names, markers, node IDs, or file paths.
+
+Because this is a standard pytest hook, its placement also matters.
+An implementation in a nested ``conftest.py`` applies to tests collected under that directory.
+Use this when a whole package or directory should share the same factory set.
+
+For declaring factories without item-specific logic, see :doc:`custom_loop_factory`.
+
+For selecting a subset of available factories from a test, see :doc:`run_test_with_specific_loop_factories`.

pytest_asyncio-1.4.0/docs/how-to-guides/custom_loop_factory.rst

@@ -0,0 +1,26 @@
+================================================
+How to use custom event loop factories for tests
+================================================
+
+pytest-asyncio can run asynchronous tests with custom event loop factories by implementing ``pytest_asyncio_loop_factories`` in ``conftest.py``. The hook provides the named event loop factories that are available for a test item by returning a mapping from factory names to loop factory callables:
+
+.. code-block:: python
+
+   import asyncio
+
+   import pytest
+
+
+   class CustomEventLoop(asyncio.SelectorEventLoop):
+       pass
+
+
+   def pytest_asyncio_loop_factories(config, item):
+       return {
+           "stdlib": asyncio.new_event_loop,
+           "custom": CustomEventLoop,
+       }
+
+The hook receives the current pytest ``item``, so it can return different factory mappings for different tests. See :doc:`configure_loop_factories_per_test` for item-based factory configuration.
+
+To run a test with only some configured factories, see :doc:`run_test_with_specific_loop_factories`.

{pytest_asyncio-1.2.0 → pytest_asyncio-1.4.0}/docs/how-to-guides/index.rst

@@ -10,6 +10,9 @@ How-To Guides
   change_fixture_loop
   change_default_fixture_loop
   change_default_test_loop
+  custom_loop_factory
+  configure_loop_factories_per_test
+  run_test_with_specific_loop_factories
   run_class_tests_in_same_loop
   run_module_tests_in_same_loop
   run_package_tests_in_same_loop

{pytest_asyncio-1.2.0 → pytest_asyncio-1.4.0}/docs/how-to-guides/migrate_from_0_23.rst

@@ -1,3 +1,5 @@
+.. _how_to_guides/migrate_from_0_23:
+
 ========================================
 How to migrate from pytest-asyncio v0.23
 ========================================

{pytest_asyncio-1.2.0 → pytest_asyncio-1.4.0}/docs/how-to-guides/multiple_loops.rst

@@ -2,6 +2,10 @@
 How to test with different event loops
 ======================================
 
+.. warning::
+
+   Overriding the *event_loop_policy* fixture is deprecated and will be removed in a future version of pytest-asyncio. Use the ``pytest_asyncio_loop_factories`` hook instead. See :doc:`custom_loop_factory` for details.
+
 Parametrizing the *event_loop_policy* fixture parametrizes all async tests. The following example causes all async tests to run multiple times, once for each event loop in the fixture parameters:
 
 .. include:: multiple_loops_example.py

pytest_asyncio-1.4.0/docs/how-to-guides/run_test_with_specific_loop_factories/conftest.py

@@ -0,0 +1,12 @@
+import asyncio
+
+
+class CustomEventLoop(asyncio.SelectorEventLoop):
+    pass
+
+
+def pytest_asyncio_loop_factories(config, item):
+    return {
+        "default": asyncio.new_event_loop,
+        "custom": CustomEventLoop,
+    }

pytest_asyncio-1.4.0/docs/how-to-guides/run_test_with_specific_loop_factories/test_loop_factories_subset.py

@@ -0,0 +1,11 @@
+import pytest
+
+
+@pytest.mark.asyncio
+async def test_runs_with_every_configured_factory():
+    pass
+
+
+@pytest.mark.asyncio(loop_factories=["custom"])
+async def test_runs_with_only_custom_factory():
+    pass

pytest_asyncio-1.4.0/docs/how-to-guides/run_test_with_specific_loop_factories.rst

@@ -0,0 +1,23 @@
+=========================================================
+How to run a test with specific event loop factories only
+=========================================================
+
+``pytest_asyncio_loop_factories`` determines which named event loop factories are available for each test item.
+By default, pytest-asyncio parametrizes a test with every factory returned for that item.
+Use ``loop_factories`` to select a subset of the factory names returned by the hook.
+
+Assume ``conftest.py`` provides two named factories:
+
+.. include:: run_test_with_specific_loop_factories/conftest.py
+   :code: python
+
+Then use ``loop_factories`` to select which available factory names a test should run with:
+
+.. include:: run_test_with_specific_loop_factories/test_loop_factories_subset.py
+   :code: python
+
+If a requested factory name is not available from the hook, the test variant for that factory is skipped.
+
+For declaring the factories themselves, see :doc:`custom_loop_factory`.
+
+For choosing the available factories from the pytest item, see :doc:`configure_loop_factories_per_test`.

pytest_asyncio-1.4.0/docs/how-to-guides/uvloop.rst

@@ -0,0 +1,41 @@
+=======================
+How to test with uvloop
+=======================
+
+Define a ``pytest_asyncio_loop_factories`` hook in your *conftest.py* that maps factory names to loop factories:
+
+.. code-block:: python
+
+    import uvloop
+
+
+    def pytest_asyncio_loop_factories(config, item):
+        return {
+            "uvloop": uvloop.new_event_loop,
+        }
+
+.. seealso::
+
+   :doc:`custom_loop_factory`
+      More details on the ``pytest_asyncio_loop_factories`` hook, including per-test factory selection and multiple factory parametrization.
+
+Using the event_loop_policy fixture
+-----------------------------------
+
+.. note::
+
+   ``asyncio.AbstractEventLoopPolicy`` is deprecated as of Python 3.14 (removal planned for 3.16), and ``uvloop.EventLoopPolicy`` will be removed alongside it. Overriding the *event_loop_policy* fixture is also deprecated in pytest-asyncio. Prefer the hook approach above.
+
+For older versions of Python and uvloop, you can override the *event_loop_policy* fixture in your *conftest.py:*
+
+.. code-block:: python
+
+    import pytest
+    import uvloop
+
+
+    @pytest.fixture(scope="session")
+    def event_loop_policy():
+        return uvloop.EventLoopPolicy()
+
+You may choose to limit the scope of the fixture to *package,* *module,* or *class,* if you only want a subset of your tests to run with uvloop.

{pytest_asyncio-1.2.0 → pytest_asyncio-1.4.0}/docs/reference/changelog.rst

@@ -6,10 +6,72 @@ All notable changes to this project will be documented in this file.
 
 The format is based on `Keep a Changelog <https://keepachangelog.com/en/1.1.0/>`__, and this project adheres to `Semantic Versioning <https://semver.org/spec/v2.0.0.html>`__.
 
-This project uses `towncrier <https://towncrier.readthedocs.io/>`__ for changlog management and the changes for the upcoming release can be found in https://github.com/pytest-dev/pytest-asyncio/tree/main/changelog.d/.
+This project uses `towncrier <https://towncrier.readthedocs.io/>`__ for changelog management and the changes for the upcoming release can be found in https://github.com/pytest-dev/pytest-asyncio/tree/main/changelog.d/.
 
 .. towncrier release notes start
 
+`1.4.0 <https://github.com/pytest-dev/pytest-asyncio/tree/1.4.0>`_ - 2026-05-26
+===============================================================================
+
+Deprecated
+----------
+
+- Overriding the *event_loop_policy* fixture is deprecated. Use the ``pytest_asyncio_loop_factories`` hook instead. (`#1419 <https://github.com/pytest-dev/pytest-asyncio/issues/1419>`_)
+
+
+Added
+-----
+
+- Added the ``pytest_asyncio_loop_factories`` hook to parametrize asyncio tests with custom event loop factories.
+
+  The hook returns a mapping of factory names to loop factories, and ``pytest.mark.asyncio(loop_factories=[...])`` selects a subset of configured factories per test. When a single factory is configured, test names are unchanged.
+
+  Synchronous ``@pytest_asyncio.fixture`` functions now see the correct event loop when custom loop factories are configured, even when test code disrupts the current event loop (e.g., via ``asyncio.run()`` or ``asyncio.set_event_loop(None)``). (`#1164 <https://github.com/pytest-dev/pytest-asyncio/issues/1164>`_)
+
+
+Changed
+-------
+
+- Improved the readability of the warning message that is displayed when ``asyncio_default_fixture_loop_scope`` is unset (`#1298 <https://github.com/pytest-dev/pytest-asyncio/issues/1298>`_)
+- Only import ``asyncio.AbstractEventLoopPolicy`` for type checking to avoid raising
+  a DeprecationWarning. (`#1394 <https://github.com/pytest-dev/pytest-asyncio/issues/1394>`_)
+- Updated minimum supported pytest version to v8.4.0. (`#1397 <https://github.com/pytest-dev/pytest-asyncio/issues/1397>`_)
+
+
+Fixed
+-----
+
+- Fixed a ``ResourceWarning: unclosed event loop`` warning that could occur when a synchronous test called ``asyncio.run()`` or otherwise unset the current event loop after pytest-asyncio had run an async test or fixture. (`#724 <https://github.com/pytest-dev/pytest-asyncio/issues/724>`_)
+
+
+Notes for Downstream Packagers
+------------------------------
+
+- Added dependency on ``sphinx-tabs >= 3.5`` to organize documentation examples into tabs. (`#1395 <https://github.com/pytest-dev/pytest-asyncio/issues/1395>`_)
+
+
+`1.3.0 <https://github.com/pytest-dev/pytest-asyncio/tree/1.3.0>`_ - 2025-11-10
+===============================================================================
+
+Removed
+-------
+
+- Support for Python 3.9 (`#1278 <https://github.com/pytest-dev/pytest-asyncio/issues/1278>`_)
+
+
+Added
+-----
+
+- Support for pytest 9 (`#1279 <https://github.com/pytest-dev/pytest-asyncio/issues/1279>`_)
+
+
+Notes for Downstream Packagers
+------------------------------
+
+- Tested Python versions include free threaded Python 3.14t (`#1274 <https://github.com/pytest-dev/pytest-asyncio/issues/1274>`_)
+- Tests are run in the same pytest process, instead of spawning a subprocess with `pytest.Pytester.runpytest_subprocess`. This prevents the test suite from accidentally using a system installation of pytest-asyncio, which could result in test errors. (`#1275 <https://github.com/pytest-dev/pytest-asyncio/issues/1275>`_)
+
+
 `1.2.0 <https://github.com/pytest-dev/pytest-asyncio/tree/1.2.0>`_ - 2025-09-12
 ===============================================================================
 
@@ -62,6 +124,10 @@ Notes for Downstream Packagers
 `1.0.0 <https://github.com/pytest-dev/pytest-asyncio/tree/1.0.0>`_ - 2025-05-26
 ===============================================================================
 
+.. seealso::
+
+   :ref:`How to migrate from pytest-asyncio v0.23 <how_to_guides/migrate_from_0_23>`
+
 Removed
 -------
 
@@ -211,6 +277,10 @@ As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the t
 This release is backwards-compatible with v0.21.
 Changes are non-breaking, unless you upgrade from v0.22.
 
+.. seealso::
+
+   :ref:`How to migrate from pytest-asyncio v0.21 <how_to_guides/migrate_from_0_21>`
+
 - BREAKING: The *asyncio_event_loop* mark has been removed. Event loops with class, module, package, and session scopes can be requested via the *scope* keyword argument to the _asyncio_ mark.
 - Introduces the *event_loop_policy* fixture which allows testing with non-default or multiple event loops  `#662 <https://github.com/pytest-dev/pytest-asyncio/pull/662>`_
 - Introduces ``pytest_asyncio.is_async_test`` which returns whether a test item is managed by pytest-asyncio `#376 <https://github.com/pytest-dev/pytest-asyncio/issues/376>`_

{pytest_asyncio-1.2.0 → pytest_asyncio-1.4.0}/docs/reference/fixtures/index.rst

@@ -4,6 +4,11 @@ Fixtures
 
 event_loop_policy
 =================
+
+.. warning::
+
+   Overriding the *event_loop_policy* fixture is deprecated and will be removed in a future version of pytest-asyncio. Use the ``pytest_asyncio_loop_factories`` hook instead. See :doc:`../hooks` for details.
+
 Returns the event loop policy used to create asyncio event loops.
 The default return value is *asyncio.get_event_loop_policy().*