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 adamnelson
Recipients adamnelson, docs@python, orsenthil, r.david.murray
Date 2010-05-25.17:41:51
SpamBayes Score 0.01473563
Marked as misclassified No
Message-id <1274809314.18.0.171067848435.issue8818@psf.upfronthosting.co.za>
In-reply-to
Content
Ok, you're right:

>>> urlsplit('cnn.com')
SplitResult(scheme='', netloc='', path='cnn.com', query='', fragment='')
>>> urlsplit('//cnn.com')
SplitResult(scheme='', netloc='cnn.com', path='', query='', fragment='')
>>> 

Although I see that nowhere in the documentation.  It seems to me that in the scenario most people are dealing with, where they are getting 'cnn.com' or 'http://cnn.com' but don't know which ahead of time, this will be useless.  I don't see who would ever have '//cnn.com' without constructing that string specifically for urlsplit.

I would propose that '/whatever' becomes the path because it starts with slash, otherwise, it becomes the netloc and everything after the first slash becomes the path.
History
Date User Action Args
2010-05-25 17:41:54adamnelsonsetrecipients: + adamnelson, orsenthil, r.david.murray, docs@python
2010-05-25 17:41:54adamnelsonsetmessageid: <1274809314.18.0.171067848435.issue8818@psf.upfronthosting.co.za>
2010-05-25 17:41:51adamnelsonlinkissue8818 messages
2010-05-25 17:41:51adamnelsoncreate