From: Oz N Tiram <oz.tiram@noris.de>
Date: Wed, 15 Jan 2020 23:55:13 +0000 (+0100)
Subject: bpo-39348: Fix code highlight for the SOCK_NONBLOCK example (GH-18018)
X-Git-Tag: v3.9.0a3~57
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=fad8b5674c66d9e00bb788e30adddb0c256c787b;p=thirdparty%2FPython%2Fcpython.git

bpo-39348: Fix code highlight for the SOCK_NONBLOCK example (GH-18018)



The previous double colon was wrongly place directly after Therefore.
Which produced a block without syntax highlighting. This fixes it
by separating the double colon from the text. As a result, sphinx now
properly highlights the python code.




https://bugs.python.org/issue39348
---

diff --git a/Doc/library/socket.rst b/Doc/library/socket.rst
index 2d7ca33f2927..2cc946c519d4 100755
--- a/Doc/library/socket.rst
+++ b/Doc/library/socket.rst
@@ -565,7 +565,9 @@ The following functions all create :ref:`socket objects <socket-objects>`.
       When :const:`SOCK_NONBLOCK` or :const:`SOCK_CLOEXEC`
       bit flags are applied to *type* they are cleared, and
       :attr:`socket.type` will not reflect them.  They are still passed
-      to the underlying system `socket()` call.  Therefore::
+      to the underlying system `socket()` call.  Therefore,
+
+      ::
 
           sock = socket.socket(
               socket.AF_INET,