Message 102911 - Python tracker

➜

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.

Author	tlocke
Recipients	eric.araujo, jjlee, ndim, orsenthil, pitrou, sergiomb2, tlocke
Date	2010-04-11.23:09:09
SpamBayes Score	4.3096172e-08
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
Regarding the RFC list issue, I've posted a new patch with a new RFC list that combines ndim's list and the comments from #5650. Pitrou argues that http://dead:beef::]/foo/ should fail because it's a malformed URL. My response would be that the parse() function has historically assumed that a URL is well formed, and so this change to accommodate IPv6 should continue to assume the URL is well formed. I'd say that a separate bug should be raised if it's thought that parse() should be changed to check that any URL is well-formed.

Regarding the RFC list issue, I've posted a new patch with a new RFC list that combines ndim's list and the comments from #5650.

Pitrou argues that http://dead:beef::]/foo/ should fail because it's a malformed URL. My response would be that the parse() function has historically assumed that a URL is well formed, and so this change to accommodate IPv6 should continue to assume the URL is well formed.

I'd say that a separate bug should be raised if it's thought that parse() should be changed to check that any URL is well-formed.

History
Date	User	Action	Args
2010-04-11 23:09:12	tlocke	set	recipients: + tlocke, jjlee, orsenthil, pitrou, ndim, eric.araujo, sergiomb2
2010-04-11 23:09:11	tlocke	set	messageid: <[email protected]>
2010-04-11 23:09:10	tlocke	link	issue2987 messages
2010-04-11 23:09:10	tlocke	create