https://github.com/python/cpython/commit/c675eb161e2a5228e6d4be7e460a54384b6634eb commit: c675eb161e2a5228e6d4be7e460a54384b6634eb branch: 3.14 author: Miss Islington (bot) <[email protected]> committer: hugovk <[email protected]> date: 2026-09-15T16:14:57+03:00 summary:
[3.14] gh-115426: Fix cross-references to `socket.socket.close()` (GH-157295) (#157331) Co-authored-by: Jade <[email protected]> files: M Doc/library/socket.rst diff --git a/Doc/library/socket.rst b/Doc/library/socket.rst index 71f5fb6ab0cc75..d1a332f74e0370 100644 --- a/Doc/library/socket.rst +++ b/Doc/library/socket.rst @@ -1481,7 +1481,7 @@ Socket Objects of :meth:`socket.getpeername` but not the actual OS resource. Unlike :func:`socket.fromfd`, *fileno* will return the same socket and not a duplicate. This may help close a detached socket using - :meth:`socket.close`. + :meth:`~socket.socket.close`. The newly created socket is :ref:`non-inheritable <fd_inheritance>`. @@ -1528,7 +1528,7 @@ Socket Objects .. versionchanged:: 3.2 Support for the :term:`context manager` protocol was added. Exiting the - context manager is equivalent to calling :meth:`~socket.close`. + context manager is equivalent to calling :meth:`~socket.socket.close`. .. method:: accept() @@ -1753,7 +1753,7 @@ Socket Objects Closing the file object returned by :meth:`makefile` won't close the original socket unless all other file objects have been closed and - :meth:`socket.close` has been called on the socket object. + :meth:`~socket.socket.close` has been called on the socket object. .. note:: _______________________________________________ Python-checkins mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3//lists/python-checkins.python.org Member address: [email protected]
