Message238982
| 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 | <1427088361.23.0.436209059714.issue20271@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-03-23 05:26:01 | martin.panter | set | recipients: + martin.panter, gvanrossum, orsenthil, vstinner, serhiy.storchaka, yselivanov, demian.brecht |
| 2015-03-23 05:26:01 | martin.panter | set | messageid: <1427088361.23.0.436209059714.issue20271@psf.upfronthosting.co.za> |
| 2015-03-23 05:26:01 | martin.panter | link | issue20271 messages |
| 2015-03-23 05:26:01 | martin.panter | create | |