This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: urlparse - relative url parsing and joins to be RFC3986 compliance
Type: enhancement Stage:
Components: Library (Lib) Versions: Python 3.4, Python 3.5
Status: open Resolution:
Dependencies: Superseder:
Assigned To: orsenthil Nosy List: gregory.p.smith, jjlee, martin.panter, orsenthil
Priority: normal Keywords: patch

Created on 2008-08-22 12:54 by orsenthil, last changed 2022-04-11 14:56 by admin.

File name Uploaded Description Edit
urlparse_rfc3986-py26.diff orsenthil, 2008-08-22 12:54 review
urlparse_rfc3986-py3k.diff orsenthil, 2008-08-22 12:55 review
Messages (6)
msg71743 - (view) Author: Senthil Kumaran (orsenthil) * (Python committer) Date: 2008-08-22 12:54
Attaching two patches to make the current urlparse library, especially 
the relative url parsing and urljoin  to be RFC3986 compliance.
I have included all the tests prescribed in RFC3986 and verified them 
to pass with the patches.

Our parsing functionality of netloc (to 
username,password,hostname,port) is same as what RFC3986 specifies. It 
uses the term 'authority' instead of 'netloc'. I did not feel the need 
for name change. If required, it can done.
msg72067 - (view) Author: Gregory P. Smith (gregory.p.smith) * (Python committer) Date: 2008-08-28 06:46
given where we are in the release process at the moment I doubt this can
go into 2.6/3.0.  Bring it up on python-dev if you have compelling
reasons why it should.

Otherwise, looks good for trunk 2.7/3.1 immediately after the releases
are branched.
msg74851 - (view) Author: John J Lee (jjlee) Date: 2008-10-16 19:41
There are a bunch of other candidate implementations of this RFC kicking
around, I think.

Also, I believe there was agreement on python-dev that a new module
should be added rather than changing the behaviour of module urlparse.
msg74852 - (view) Author: John J Lee (jjlee) Date: 2008-10-16 19:44
Here they are:
msg74856 - (view) Author: John J Lee (jjlee) Date: 2008-10-16 20:38
Hmm, I see you've already commented on some of those, Senthil.  Perhaps
you could add a comment to this bug explaining how your patch relates to
the others.  Should it replace them? (why?)  Should one of those patches
be applied also?

Also, my comment about there being agreement on python-dev is probably a
misrepresentation.  This is what I remembered, I think:

which seems to say that a new API should be added, but not that urlparse
shouldn't be changed to be more compliant with RFC 3986.
msg109962 - (view) Author: Senthil Kumaran (orsenthil) * (Python committer) Date: 2010-07-11 05:16
Several changes were already made to urlparse to make it more rfc3986 compliant. Let me recollect what else these patches offer.
Date User Action Args
2022-04-11 14:56:38adminsetgithub: 47897
2015-02-09 00:10:27martin.pantersetnosy: + martin.panter
2014-06-26 19:07:57BreamoreBoysetversions: + Python 3.4, Python 3.5, - Python 3.2
2010-07-11 05:16:10orsenthilsetassignee: gregory.p.smith -> orsenthil
messages: + msg109962
2010-07-10 06:07:54terry.reedysetversions: + Python 3.2, - Python 2.6, Python 3.0
2008-10-16 20:38:25jjleesetmessages: + msg74856
2008-10-16 19:44:46jjleesetmessages: + msg74852
2008-10-16 19:41:55jjleesetnosy: + jjlee
messages: + msg74851
2008-08-28 06:46:59gregory.p.smithsetpriority: normal
assignee: gregory.p.smith
type: enhancement
messages: + msg72067
nosy: + gregory.p.smith
2008-08-22 12:55:00orsenthilsetfiles: + urlparse_rfc3986-py3k.diff
2008-08-22 12:54:34orsenthilcreate