From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Mon, 26 Sep 2022 22:45:58 +0000 (-0700)
Subject: GH-65046: Fix docs about logging in `asyncio` (GH-97559)
X-Git-Tag: v3.11.0~55
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=e65e6de0fbfdb1e030b3ba067913e953dff2257f;p=thirdparty%2FPython%2Fcpython.git

GH-65046: Fix docs about logging in `asyncio` (GH-97559)


Explain that logging should not use network I/O.
(cherry picked from commit d68c37c0d08542a346a13b150a204208bb0408f5)

Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com>
---

diff --git a/Doc/library/asyncio-dev.rst b/Doc/library/asyncio-dev.rst
index 921a394a59fe..14f2c3533c97 100644
--- a/Doc/library/asyncio-dev.rst
+++ b/Doc/library/asyncio-dev.rst
@@ -149,8 +149,7 @@ adjusted::
 
 
 Network logging can block the event loop. It is recommended to use
-a separate thread for handling logs or use non-blocking IO. For example,
-see :ref:`blocking-handlers`.
+a separate thread for handling logs or use non-blocking IO.
 
 
 .. _asyncio-coroutine-not-scheduled: