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 | orsenthil |
|---|---|
| Recipients | facundobatista, georg.brandl, georg.brandl, kruegi, orsenthil, sjones |
| Date | 2008年06月10日.02:54:27 |
| SpamBayes Score | 0.0010794895 |
| Marked as misclassified | No |
| Message-id | <1213066468.71.0.143409672034.issue754016@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Attaching the patch to fix this issue. I deliberated upon this for a
while and came up with the approach to:
1) fix the port issue, wherein urlparse should technically recognize the
':' separator for port from ':' after scheme.
2) And Doc fix wherein, it is advised that in the absence of a scheme,
use the net_loc as //net_loc (following RCF 1808).
If we go for any other fix, like internally pre-pending // when user has
not specified the scheme (like in many pratical purpose), then we stand
at chance of breaking a number of tests ( cases where url is 'g'(path
only),';x' (path with params) and cases where relative url is g:h)
Let me know your thoughts on this.
>>> urlparse('1.2.3.4:80')
ParseResult(scheme='', netloc='', path='1.2.3.4:80', params='',
query='', fragment='')
>>> urlparse('http://www.python.org:80/~guido/foo?query#fun')
ParseResult(scheme='http', netloc='www.python.org:80',
path='/~guido/foo', params='', query='query', fragment='fun')
>>> |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年06月10日 02:54:29 | orsenthil | set | spambayes_score: 0.00107949 -> 0.0010794895 recipients: + orsenthil, georg.brandl, facundobatista, birkenfeld, sjones, kruegi |
| 2008年06月10日 02:54:28 | orsenthil | set | spambayes_score: 0.00107949 -> 0.00107949 messageid: <1213066468.71.0.143409672034.issue754016@psf.upfronthosting.co.za> |
| 2008年06月10日 02:54:28 | orsenthil | link | issue754016 messages |
| 2008年06月10日 02:54:27 | orsenthil | create | |