From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Mon, 24 Oct 2022 18:01:37 +0000 (-0700) Subject: GH-91635: clarify docs about closing of transport in asyncio (GH-98563) X-Git-Tag: v3.10.9~131 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=39e914c03aa14c60c78b93f126eb845cea18b3d9;p=thirdparty%2FPython%2Fcpython.git GH-91635: clarify docs about closing of transport in asyncio (GH-98563) (cherry picked from commit 2fdcc6f2cb5e3e1e09b8dff179f4c11193799998) Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com> --- diff --git a/Doc/library/asyncio-protocol.rst b/Doc/library/asyncio-protocol.rst index 969354ceb163..7bc906eaafc1 100644 --- a/Doc/library/asyncio-protocol.rst +++ b/Doc/library/asyncio-protocol.rst @@ -156,7 +156,8 @@ Base Transport will be received. After all buffered data is flushed, the protocol's :meth:`protocol.connection_lost() ` method will be called with - :const:`None` as its argument. + :const:`None` as its argument. The transport should not be + used once it is closed. .. method:: BaseTransport.is_closing()