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 demian.brecht
Recipients demian.brecht, gvanrossum, martin.panter, orsenthil, serhiy.storchaka, vstinner, yselivanov
Date 2015-03-06.18:59:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> splitport() shouldn't handle auth, it should be called after auth is dropped with splituser().

Why shouldn't splitport() handle auth? Are you suggesting that in the eyes of splitport() that "user:password@host:port" should be invalid?

>>> parse.splitport('user:password@host:80')
('user:password@host', '80')

Seems to be reasonable behaviour to me. Why add the artificial constraint of calling splituser() first?
Date User Action Args
2015-03-06 18:59:25demian.brechtsetrecipients: + demian.brecht, gvanrossum, orsenthil, vstinner, martin.panter, serhiy.storchaka, yselivanov
2015-03-06 18:59:25demian.brechtsetmessageid: <>
2015-03-06 18:59:25demian.brechtlinkissue20271 messages
2015-03-06 18:59:25demian.brechtcreate