Fred L. Drake, Jr. <fdr...@acm.org> added the comment: On Tue, May 25, 2010 at 1:41 PM, AdamN <rep...@bugs.python.org> wrote: > Although I see that nowhere in the documentation.
It needn't be in the urlparse documentation; the RFCs on URL syntax apply here. None of what's going on with the urlparse module is Python specific, as far as the URL interpretation is concerned. > 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. 'cnn.com' isn't a URL, and there's no need for urlparse to handle it direectly. That just complicates things. Doing something above and beyond what the RFCs specify means you need to really think about the heuristics you're applying. If there's a useful set of heuristics that folks can agree on, that's a good case for a new module distributed on PyPI. -Fred ---------- nosy: +fdrake _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8818> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
