From f8757fd356936c800435f3270fff7a5c5df6dcb4 Mon Sep 17 00:00:00 2001 From: Georg Brandl Date: Sun, 12 Oct 2014 16:13:32 +0200 Subject: [PATCH] Closes #22586: clarify meaning of allow_fragments in urlparse. --- Doc/library/urlparse.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Doc/library/urlparse.rst b/Doc/library/urlparse.rst index 1bc361d8b2..87e08dd47f 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: -- 2.50.1