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: v2.7.9rc1~137^2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=f8757fd356936c800435f3270fff7a5c5df6dcb4;p=thirdparty%2FPython%2Fcpython.git

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

diff --git a/Doc/library/urlparse.rst b/Doc/library/urlparse.rst
index 1bc361d8b264..87e08dd47f9c 100644
--- a/Doc/library/urlparse.rst
+++ b/Doc/library/urlparse.rst
@@ -83,8 +83,9 @@ The :mod:`urlparse` module defines the following functions:
    this argument is the empty string.
 
    If the *allow_fragments* argument is false, fragment identifiers are not
-   allowed, even if the URL's addressing scheme normally does support them.  The
-   default value for this argument is :const:`True`.
+   recognized and parsed as part of the preceding component, even if the URL's
+   addressing scheme normally does support them.  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: