[ python-Bugs-1591035 ] update urlparse to RFC 3986
SourceForge.net
noreply at sourceforge.net
Mon Nov 6 10:47:42 CET 2006
Bugs item #1591035, was opened at 2006-11-05 15:27
Message generated for change (Comment added) made by dalke
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1591035&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Feature Request
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Andrew Dalke (dalke)
Assigned to: Nobody/Anonymous (nobody)
Summary: update urlparse to RFC 3986
Initial Comment:
urlparse implements RFC 1808. That is strongly out of
date. The most recent is RFC 3986.
Here is a text from 4Suite
# Reasons to avoid using urllib.basejoin() and
urlparse.urljoin():
# - Both are partial implementations of
long-obsolete specs.
# - Both accept relative URLs as the base, which no
spec allows.
# - urllib.basejoin() mishandles the '' and '..'
references.
# - If the base URL uses a non-hierarchical or
relative path,
# or if the URL scheme is unrecognized, the
result is not
# always as expected (partly due to issues in
RFC 1808).
# - If the authority component of a 'file' URI is
empty,
# the authority component is removed altogether.
If it was
# not present, an empty authority component is
in the result.
# - '.' and '..' segments are not always collapsed
as well as they
# should be (partly due to issues in RFC 1808).
# - Effective Python 2.4, urllib.basejoin() *is*
urlparse.urljoin(),
# but urlparse.urljoin() is still based on RFC 1808.
See also the back python-dev discussions on "urlparse"
for examples of people wanting a better/more up-to-date
urlparse/urljoin.
----------------------------------------------------------------------
>Comment By: Andrew Dalke (dalke)
Date: 2006-11-06 02:47
Message:
Logged In: YES
user_id=190903
See also bug 1462525 which has a 'uriparse.py' replacement
for urlparse, claiming better compliance.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1591035&group_id=5470
More information about the Python-bugs-list
mailing list