From f4fd0678cd1bf962e7a9f84ee8a35b749755aca2 Mon Sep 17 00:00:00 2001 From: Alexander Ershov <150328014+AEErshov@users.noreply.github.com> Date: Sun, 30 Mar 2025 15:19:36 +0700 Subject: [PATCH] gh-129994: update docs when using `dualstack_ipv6` in `socket.create_server` (GH-129996) (cherry picked from commit 044a1e13d5cfc91b0a8774e936877e91cbac3a16) Co-authored-by: Alexander Ershov <150328014+AEErshov@users.noreply.github.com> --- Doc/library/socket.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Doc/library/socket.rst b/Doc/library/socket.rst index 12f95b839a948e..e5baa3a002a01e 100644 --- a/Doc/library/socket.rst +++ b/Doc/library/socket.rst @@ -838,10 +838,10 @@ The following functions all create :ref:`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.