[issue7904] urllib.urlparse mishandles novel schemes

mARK added the comment: it's not actually necessary to have a list of known schemes. any url that has a double slash after the colon is expected to follow that with an authority section (what urlparse calls "netloc"), optionally followed by a path, which starts with a slash. there are vario

[issue7904] urllib.urlparse mishandles novel schemes

Senthil Kumaran added the comment: Does s3 stand for the amazon s3 services? urlparse does not have it under its list of known schemes yet. Does s3 have any specifications as such or is aligned towards any of the known schemes (like http or ftp)? s3 is valid scheme name according to rfc 3986,

[issue7904] urllib.urlparse mishandles novel schemes

Ezio Melotti added the comment: Thanks for the report, could you provide a patch with unit tests? -- nosy: +ezio.melotti priority: -> normal stage: -> test needed versions: +Python 2.6, Python 2.7 -Python 2.5 ___ Python tracker

[issue7904] urllib.urlparse mishandles novel schemes

New submission from mARK : urlparse.urlsplit('s3://example/files/photos/161565.jpg') returns ('s3', '', '//example/files/photos/161565.jpg', '', '') instead of ('s3', 'example', '/files/photos/161565.jpg', '', '') according to rfc 3986 's3' is a valid scheme name, so the '://' indicates a URL w