8000 [3.12] gh-129994: update docs when using `dualstack_ipv6` in `socket.… · python/cpython@f1b65d7 · GitHub
[go: up one dir, main page]

Skip to content

Commit f1b65d7

Browse files
[3.12] gh-129994: update docs when using dualstack_ipv6 in socket.create_server (GH-129996) (#131891)
gh-129994: update docs when using `dualstack_ipv6` in `socket.create_server` (GH-129996) (cherry picked from commit 044a1e1) Co-authored-by: Alexander Ershov <150328014+AEErshov@users.noreply.github.com>
1 parent 85b6b0e commit f1b65d7

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

Doc/library/socket.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -833,10 +833,10 @@ The following functions all create :ref:`socket objects <socket-objects>`.
833833
, a default reasonable value is chosen.
834834
*reuse_port* dictates whether to set the :data:`SO_REUSEPORT` socket option.
835835

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

0 commit comments

Comments
 (0)
0