From: AN Long <aisk@users.noreply.github.com>
Date: Mon, 28 Jul 2025 10:55:59 +0000 (+0900)
Subject: gh-119711: describe `create_datagram_endpoint`'s behavior in asyncio when `local_addr... 
X-Git-Tag: v3.15.0a1~834
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1481384141342479b3ba4b89f653b4e5bef0d272;p=thirdparty%2FPython%2Fcpython.git

gh-119711: describe `create_datagram_endpoint`'s behavior in asyncio when `local_addr` is `None` (#136913)
---

diff --git a/Doc/library/asyncio-eventloop.rst b/Doc/library/asyncio-eventloop.rst
index 91970c282391..9561c40776f0 100644
--- a/Doc/library/asyncio-eventloop.rst
+++ b/Doc/library/asyncio-eventloop.rst
@@ -611,6 +611,12 @@ Opening network connections
      to bind the socket locally.  The *local_host* and *local_port*
      are looked up using :meth:`getaddrinfo`.
 
+     .. note::
+
+        On Windows, when using the proactor event loop with ``local_addr=None``,
+        an :exc:`OSError` with :attr:`!errno.WSAEINVAL` will be raised
+        when running it.
+
    * *remote_addr*, if given, is a ``(remote_host, remote_port)`` tuple used
      to connect the socket to a remote address.  The *remote_host* and
      *remote_port* are looked up using :meth:`getaddrinfo`.