Message120678
| Author |
orsenthil |
| Recipients |
belopolsky, docs@python, eric.araujo, georg.brandl, orsenthil, r.david.murray |
| Date |
2010年11月07日.13:21:57 |
| SpamBayes Score |
2.3683253e-06 |
| Marked as misclassified |
No |
| Message-id |
<1289136121.25.0.718608734675.issue10226@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Fixed the wordings in r86296(py3k), r86297(release31-maint) and r86298(release27-maint).
David, for the examples you mentioned, the first one's parsing logic follows the explanation that is written. It is correct.
For the second example, the port value not being a DIGIT exhibits such a behavior. I am unable to recollect the reason for this behavior.
Either the URL is invalid (PORT is not a DIGIT, and parse module is simply ignoring to raise an error - it's okay, given the input is invalid) or it needs to distinguish the ':' as a port separator from path separator for some valid urls.
I think, if we find a better reason to change something for the second scenario, we shall address that. |
|