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 Buck.Golemon, ankitoshniwal, ezio.melotti, orsenthil
Date 2012-06-29.11:07:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Look at the following two bugs which dwelt on similar issues: Issue8339 and Issue7904 and in one message particular, msg102737, I seem to have come to a conclusion that " I don't see that 'x://' and 'x:///y' qualifies as valid URLS as per RFC 3986"   and it applies to this bug too where the url is requested as yelp:///x 

Does yelp://localhost/x be a way to access in your case? That would be consistent with specification. Or in your code, you can add 'yelp' to uses_netloc list and then expect the desired behavior.

from urlparse import uses_netloc

I understand that, using of the uses_netloc is a limitation, but given the requirements of both absolute and relative parsing that lists has served a useful behavior.

I would like to close this one for the above mention points and open a feature request (or convert this to a feature request) which asks to remove the dependency of uses_netloc in urlparse. Does this resolution sound okay?
Date User Action Args
2012-06-29 11:07:33orsenthilsetrecipients: + orsenthil, ezio.melotti, Buck.Golemon, ankitoshniwal
2012-06-29 11:07:33orsenthilsetmessageid: <>
2012-06-29 11:07:32orsenthillinkissue15009 messages
2012-06-29 11:07:31orsenthilcreate