Skip to content

gh-119711: Describe create_datagram_endpoint's behavior in asyncio when local_addr is None #136913

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 28, 2025
Merged

gh-119711: Describe create_datagram_endpoint's behavior in asyncio when local_addr is None #136913

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d42d979
Update create_datagram_endpoint's doc in asyncio while local_addr=None
aisk Jul 21, 2025
ded229c
Fix document build on non Windows platform
aisk Jul 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions Doc/library/asyncio-eventloop.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`.
Expand Down
Loading