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 orsenthil
Recipients asvetlov, jfinkels, mykmelez, orsenthil, r.david.murray, webwin
Date 2013-04-09.05:34:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365485692.51.0.338566365773.issue6640@psf.upfronthosting.co.za>
In-reply-to
Content
RFC3986 bears the weightage since urlparse aims to satisfy that. As per that, mailto should return the url as path, and current urlparse behaves properly.

$ ./python.exe
Python 3.4.0a0 (default:50164abbfc98+, Apr  8 2013, 22:19:34)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import urllib.parse
>>> urllib.parse.urlparse("mailto:foo@example.com?subject=hi")
ParseResult(scheme='mailto', netloc='', path='foo@example.com', params='', query='subject=hi', fragment='')
>>>

So, I am closing this bug as won't fix.
History
Date User Action Args
2013-04-09 05:34:52orsenthilsetrecipients: + orsenthil, r.david.murray, asvetlov, mykmelez, jfinkels, webwin
2013-04-09 05:34:52orsenthilsetmessageid: <1365485692.51.0.338566365773.issue6640@psf.upfronthosting.co.za>
2013-04-09 05:34:52orsenthillinkissue6640 messages
2013-04-09 05:34:52orsenthilcreate