From: Georg Brandl <georg@python.org>
Date: Sun, 11 Jul 2010 09:23:11 +0000 (+0000)
Subject: #6774: explain shutdown() behavior varying with platform.
X-Git-Tag: v3.2a1~230
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=0104bcdb801b643eeb9f1845e026fcefdecfc48e;p=thirdparty%2FPython%2Fcpython.git

#6774: explain shutdown() behavior varying with platform.
---

diff --git a/Doc/library/socket.rst b/Doc/library/socket.rst
index 1cc0f0421813..75d86b7cf710 100644
--- a/Doc/library/socket.rst
+++ b/Doc/library/socket.rst
@@ -748,7 +748,9 @@ timeout error of its own regardless of any Python socket timeout setting.
    Shut down one or both halves of the connection.  If *how* is :const:`SHUT_RD`,
    further receives are disallowed.  If *how* is :const:`SHUT_WR`, further sends
    are disallowed.  If *how* is :const:`SHUT_RDWR`, further sends and receives are
-   disallowed.
+   disallowed.  Depending on the platform, shutting down one half of the connection
+   can also close the opposite half (e.g. on Mac OS X, ``shutdown(SHUT_WR)`` does
+   not allow further reads on the other end of the connection).
 
 Note that there are no methods :meth:`read` or :meth:`write`; use
 :meth:`~socket.recv` and :meth:`~socket.send` without *flags* argument instead.