[issue3647] urlparse - relative url parsing and joins to be RFC3986 compliance

[Terry J. Reedy]

Changes by Terry J. Reedy :


--
versions: +Python 3.2 -Python 2.6, Python 3.0

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3647] urlparse - relative url parsing and joins to be RFC3986 compliance

[Senthil Kumaran]

Senthil Kumaran  added the comment:

Several changes were already made to urlparse to make it more rfc3986 
compliant. Let me recollect what else these patches offer.

--
assignee: gregory.p.smith -> orsenthil

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3647] urlparse - relative url parsing and joins to be RFC3986 compliance

[Senthil]

New submission from Senthil <[EMAIL PROTECTED]>:

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.

--
components: Library (Lib)
files: urlparse_rfc3986-py26.diff
keywords: patch
messages: 71743
nosy: orsenthil
severity: normal
status: open
title: urlparse - relative url parsing and joins to be RFC3986 compliance
versions: Python 2.6, Python 3.0
Added file: http://bugs.python.org/file11208/urlparse_rfc3986-py26.diff

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3647] urlparse - relative url parsing and joins to be RFC3986 compliance

[Senthil]

Changes by Senthil <[EMAIL PROTECTED]>:


Added file: http://bugs.python.org/file11209/urlparse_rfc3986-py3k.diff

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3647] urlparse - relative url parsing and joins to be RFC3986 compliance

[Gregory P. Smith]

Gregory P. Smith <[EMAIL PROTECTED]> added the comment:

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.

--
assignee:  -> gregory.p.smith
nosy: +gregory.p.smith
priority:  -> normal
type:  -> feature request

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3647] urlparse - relative url parsing and joins to be RFC3986 compliance

[John J Lee]

John J Lee <[EMAIL PROTECTED]> added the comment:

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.

--
nosy: +jjlee

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3647] urlparse - relative url parsing and joins to be RFC3986 compliance

[John J Lee]

John J Lee <[EMAIL PROTECTED]> added the comment:

Here they are:

http://bugs.python.org/issue1500504
http://bugs.python.org/issue1462525
http://bugs.python.org/issue1591035

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue3647] urlparse - relative url parsing and joins to be RFC3986 compliance

[John J Lee]

John J Lee <[EMAIL PROTECTED]> added the comment:

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:

http://article.gmane.org/gmane.comp.python.devel/73314/

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.

___
Python tracker <[EMAIL PROTECTED]>

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com