Message179533
Thank you for you feedback. I agree, the reason I wanted this was because of a corner case, but otoh, the username:password syntax is the real corner case imho. Of course, I understand that this must be supported for backwards compatability.
(For fully RFC compliant URLs however, userinfo would be the same as user since : in userinfo isn't allowed, so again, you have a very valid point for your corner case argument.)
The patch was developed against 2.7, so it won't apply on 3.4, but looking at 3.4, urlparse already has a _userinfo property method, but it splits the userinfo in a tuple of (username, password). It would be easy to adapt the change to 3.4, but I'll wait until I get additional feedback. |
|
Date |
User |
Action |
Args |
2013-01-10 08:24:21 | olof | set | recipients:
+ olof, orsenthil |
2013-01-10 08:24:21 | olof | set | messageid: <1357806261.44.0.00514180264563.issue16909@psf.upfronthosting.co.za> |
2013-01-10 08:24:21 | olof | link | issue16909 messages |
2013-01-10 08:24:20 | olof | create | |
|