Message237371
| 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 | <1425668365.87.0.692607381515.issue20271@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> 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? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-03-06 18:59:25 | demian.brecht | set | recipients: + demian.brecht, gvanrossum, orsenthil, vstinner, martin.panter, serhiy.storchaka, yselivanov |
| 2015-03-06 18:59:25 | demian.brecht | set | messageid: <1425668365.87.0.692607381515.issue20271@psf.upfronthosting.co.za> |
| 2015-03-06 18:59:25 | demian.brecht | link | issue20271 messages |
| 2015-03-06 18:59:25 | demian.brecht | create | |