From: Alexander Ershov <150328014+AEErshov@users.noreply.github.com>
Date: Sun, 30 Mar 2025 08:19:36 +0000 (+0700)
Subject: gh-129994: update docs when using `dualstack_ipv6` in `socket.create_server` (#129996)
X-Git-Tag: v3.14.0a7~145
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=044a1e13d5cfc91b0a8774e936877e91cbac3a16;p=thirdparty%2FPython%2Fcpython.git

gh-129994: update docs when using `dualstack_ipv6` in `socket.create_server` (#129996)
---

diff --git a/Doc/library/socket.rst b/Doc/library/socket.rst
index bc888dc593cf..1bc7f76b5ba6 100644
--- a/Doc/library/socket.rst
+++ b/Doc/library/socket.rst
@@ -882,10 +882,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.