[3.13] gh-120866: Document behavior change of asyncio.Server.wait_closed() since...

gh-120866: Document behavior change of asyncio.Server.wait_closed() since 3.12 (GH-154676)
(cherry picked from commit 222a8bf3259b6fae2132c9278aa9ecff68a99b2a)

Co-authored-by: Kumar Aditya <kumaraditya@python.org>

diff --git a/Doc/library/asyncio-eventloop.rst b/Doc/library/asyncio-eventloop.rst
index bc4e014f7e5daff47e4a8d3e7de37a9b2490b5bf..00bbe3a7ab1db31a0aa8131eaa028efac95a2a76 100644 (file)
--- a/Doc/library/asyncio-eventloop.rst
+++ b/Doc/library/asyncio-eventloop.rst
@@ -1861,6 +1861,12 @@ Do not instantiate the :class:`Server` class directly.
       Wait until the :meth:`close` method completes and all active
       connections have finished.
 
+      .. versionchanged:: 3.12
+         ``wait_closed()`` now waits until the server is closed and
+         all active connections have finished.  Previously, it returned
+         immediately if the server was already closed, even if
+         connections were still active.
+
    .. attribute:: sockets
 
       List of socket-like objects, ``asyncio.trsock.TransportSocket``, which