From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Thu, 16 Jan 2020 00:00:32 +0000 (-0800)
Subject: bpo-39348: Fix code highlight for the SOCK_NONBLOCK example (GH-18018)
X-Git-Tag: v3.7.7rc1~89
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=970188c2d792133e2273924a987e0542659a676f;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
(cherry picked from commit fad8b5674c66d9e00bb788e30adddb0c256c787b)

Co-authored-by: Oz N Tiram <oz.tiram@noris.de>
---

diff --git a/Doc/library/socket.rst b/Doc/library/socket.rst
index 178d7da2e5f0..7e8075ebf36b 100644
--- a/Doc/library/socket.rst
+++ b/Doc/library/socket.rst
@@ -529,7 +529,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,