From 1d5ca2ad99e0edb9ed0012017ba80cc9f3c92d95 Mon Sep 17 00:00:00 2001
From: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com>
Date: Tue, 27 Sep 2022 03:57:15 +0530
Subject: [PATCH] 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>
---
 Doc/library/asyncio-dev.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Doc/library/asyncio-dev.rst b/Doc/library/asyncio-dev.rst
index 77f1128de50c95..9676a352f4b24e 100644
--- a/Doc/library/asyncio-dev.rst
+++ b/Doc/library/asyncio-dev.rst
@@ -148,6 +148,10 @@ adjusted::
    logging.getLogger("asyncio").setLevel(logging.WARNING)
 
 
+Network logging can block the event loop. It is recommended to use
+a separate thread for handling logs or use non-blocking IO.
+
+
 .. _asyncio-coroutine-not-scheduled:
 
 Detect never-awaited coroutines