From: Georg Brandl <georg@python.org>
Date: Sun, 12 Oct 2014 14:13:32 +0000 (+0200)
Subject: Closes #22586: clarify meaning of allow_fragments in urlparse.
X-Git-Tag: v3.4.3rc1~492
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=62b08136d759e0da4b9a7fa6189ce1059d7b5150;p=thirdparty%2FPython%2Fcpython.git

Closes #22586: clarify meaning of allow_fragments in urlparse.
---

diff --git a/Doc/library/urllib.parse.rst b/Doc/library/urllib.parse.rst
index b95142042d87..42aa4be170a4 100644
--- a/Doc/library/urllib.parse.rst
+++ b/Doc/library/urllib.parse.rst
@@ -81,7 +81,8 @@ or on combining URL components into a URL string.
    this argument is the empty string.
 
    If the *allow_fragments* argument is false, fragment identifiers are not
-   allowed.  The default value for this argument is :const:`True`.
+   recognized and parsed as part of the preceding component.  The default value
+   for this argument is :const:`True`.
 
    The return value is actually an instance of a subclass of :class:`tuple`.  This
    class has the following additional read-only convenience attributes: