From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Sun, 10 Aug 2025 13:52:30 +0000 (+0200)
Subject: [3.14] gh-119711: describe `create_datagram_endpoint`'s behavior in asyncio when... 
X-Git-Tag: v3.14.0rc2~18
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=f180fb956b3e03e2f9ecdf24eebf8824a75af18e;p=thirdparty%2FPython%2Fcpython.git

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

Co-authored-by: AN Long <aisk@users.noreply.github.com>
---

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`.