From 2834fdc689f52edba3ea1f9b2ee85fc33fc9e097 Mon Sep 17 00:00:00 2001 From: Serhiy Storchaka Date: Fri, 13 Jan 2023 10:15:23 +0200 Subject: [PATCH] [3.11] gh-100160: Tweak the documentation for the default asyncio policy (GH-100969) --- Doc/library/asyncio-policy.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Doc/library/asyncio-policy.rst b/Doc/library/asyncio-policy.rst index eb043b3e5e7f..f846f76ca095 100644 --- a/Doc/library/asyncio-policy.rst +++ b/Doc/library/asyncio-policy.rst @@ -113,9 +113,9 @@ asyncio ships with the following built-in policies: On Windows, :class:`ProactorEventLoop` is now used by default. .. note:: - In Python versions 3.10.9, 3.11.1 and 3.12 this function emits a - :exc:`DeprecationWarning` if there is no running event loop and no - current loop is set. + In Python versions 3.10.9, 3.11.1 and 3.12 the :meth:`get_event_loop` + method of the default asyncio policy emits a :exc:`DeprecationWarning` + if there is no running event loop and no current loop is set. In some future Python release this will become an error. -- 2.47.3