Demian Brecht added the comment:
> 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?
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue20271>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
