Message 99265 - 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	r.david.murray
Recipients	ezio.melotti, mbloore, orsenthil, r.david.murray
Date	2010-02-12.13:41:47
SpamBayes Score	1.1928623e-05
Marked as misclassified	No
Message-id	<1265982111.42.0.887755928078.issue7904@psf.upfronthosting.co.za>
In-reply-to

Content
I think Mark is correct. RFC 3986 says: When authority is present, the path must either be empty or begin with a slash ("/") character. When authority is not present, the path cannot begin with two slash characters ("//"). I think it would make sense to have urlparse fall back to doing a generic RFC 3986 parse when it does not recognize the scheme.

I think Mark is correct.  RFC 3986 says:

When authority is present, the path must either be empty or begin with a slash ("/") character.  When authority is not present, the path cannot begin with two slash characters ("//").

I think it would make sense to have urlparse fall back to doing a generic RFC 3986 parse when it does not recognize the scheme.

History
Date	User	Action	Args
2010-02-12 13:41:52	r.david.murray	set	recipients: + r.david.murray, orsenthil, ezio.melotti, mbloore
2010-02-12 13:41:51	r.david.murray	set	messageid: <1265982111.42.0.887755928078.issue7904@psf.upfronthosting.co.za>
2010-02-12 13:41:48	r.david.murray	link	issue7904 messages
2010-02-12 13:41:47	r.david.murray	create