Skip to content

[3.13] gh-129994: update docs when using dualstack_ipv6 in socket.create_server (GH-129996) #131890

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 1 commit into from
Mar 30, 2025
Merged

[3.13] gh-129994: update docs when using dualstack_ipv6 in socket.create_server (GH-129996) #131890

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions Doc/library/socket.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -838,10 +838,10 @@ The following functions all create :ref:`socket objects <socket-objects>`.
, a default reasonable value is chosen.
*reuse_port* dictates whether to set the :data:`SO_REUSEPORT` socket option.

If *dualstack_ipv6* is true and the platform supports it the socket will
be able to accept both IPv4 and IPv6 connections, else it will raise
:exc:`ValueError`. Most POSIX platforms and Windows are supposed to support
this functionality.
If *dualstack_ipv6* is true, *family* is :data:`AF_INET6` and the platform
supports it the socket will be able to accept both IPv4 and IPv6 connections,
else it will raise :exc:`ValueError`. Most POSIX platforms and Windows are
supposed to support this functionality.
When this functionality is enabled the address returned by
:meth:`socket.getpeername` when an IPv4 connection occurs will be an IPv6
address represented as an IPv4-mapped IPv6 address.
Expand Down
Loading