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 martin.panter
Recipients demian.brecht, gvanrossum, martin.panter, orsenthil, serhiy.storchaka, vstinner, yselivanov
Date 2015-03-23.05:26:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
To me, the only difference between urlsplit() and urlparse() is that urlsplit() does not treat parameters following a semicolon specially. The documentation tends to agree with this view. So whatever exceptions are raised by urlparse() should also be raised by urlsplit() for consistency.

Also, I doubt it is worth worrying about the finer details of splitport() or whatever, because they are meant to be deprecated and not used externally, except for backwards compatibility.
Date User Action Args
2015-03-23 05:26:01martin.pantersetrecipients: + martin.panter, gvanrossum, orsenthil, vstinner, serhiy.storchaka, yselivanov, demian.brecht
2015-03-23 05:26:01martin.pantersetmessageid: <>
2015-03-23 05:26:01martin.panterlinkissue20271 messages
2015-03-23 05:26:01martin.pantercreate