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 gvanrossum
Recipients gvanrossum
Date 2016-07-11.18:02:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1468260123.51.0.000787877209911.issue27485@psf.upfronthosting.co.za>
In-reply-to
Content
I've seen and written some code that uses urllib.splitport() [1], but it's not in the export list, nor in the docs. However I see no easy other way to perform the same function. Should we make it official, or get rid of it? It's used internally in urllib/request.py [2]. There's a test for it in test_urlparse.py [3], but another test [4] also acknowledges that it's "undocumented" (which suggests that the author of that test didn't know what to do with it either).

Same question for the others in that list [4]:
            'splitattr', 'splithost', 'splitnport', 'splitpasswd',
            'splitport', 'splitquery', 'splittag', 'splittype', 'splituser',
            'splitvalue',
            'Quoter', 'ResultBase', 'clear_cache', 'to_bytes', 'unwrap',

References:
[1] https://hg.python.org/cpython/file/tip/Lib/urllib/parse.py#l956
[2] https://hg.python.org/cpython/file/tip/Lib/urllib/request.py#l106
[3] https://hg.python.org/cpython/file/tip/Lib/test/test_urlparse.py#l1015
[4] https://hg.python.org/cpython/file/tip/Lib/test/test_urlparse.py#l946
History
Date User Action Args
2016-07-11 18:02:03gvanrossumsetrecipients: + gvanrossum
2016-07-11 18:02:03gvanrossumsetmessageid: <1468260123.51.0.000787877209911.issue27485@psf.upfronthosting.co.za>
2016-07-11 18:02:03gvanrossumlinkissue27485 messages
2016-07-11 18:02:03gvanrossumcreate