From 009a6bd675ed8f853d57794eacb660912be5dd49 Mon Sep 17 00:00:00 2001 From: Georg Brandl Date: Mon, 24 Jan 2011 19:59:08 +0000 Subject: [PATCH] Fix label syntax. --- Doc/library/urllib.parse.rst | 2 +- Doc/whatsnew/3.2.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/library/urllib.parse.rst b/Doc/library/urllib.parse.rst index 037d4c41c0..6a143c5fe5 100644 --- a/Doc/library/urllib.parse.rst +++ b/Doc/library/urllib.parse.rst @@ -281,7 +281,7 @@ or on combining URL components into a URL string. .. versionchanged:: 3.2 Result is a structured object rather than a simple 2-tuple. -:: _parsing-ascii-encoded-bytes: +.. _parsing-ascii-encoded-bytes: Parsing ASCII Encoded Bytes --------------------------- diff --git a/Doc/whatsnew/3.2.rst b/Doc/whatsnew/3.2.rst index b510f447e7..e846a0fe25 100644 --- a/Doc/whatsnew/3.2.rst +++ b/Doc/whatsnew/3.2.rst @@ -1887,7 +1887,7 @@ string, then the *safe*, *encoding*, and *error* parameters are sent to encoding='latin-1') 'type=telenovela&name=%BFD%F3nde+Est%E1+Elisa%3F' -As detailed in :ref:`parsing-ascii-encoded-bytes` , all the :mod:`urllib.parse` +As detailed in :ref:`parsing-ascii-encoded-bytes`, all the :mod:`urllib.parse` functions now accept ASCII-encoded byte strings as input, so long as they are not mixed with regular strings. If ASCII-encoded byte strings are given as parameters, the return types will also be an ASCII-encoded byte strings: -- 2.40.0