[issue33480] Improvement suggestions for urllib.parse.urlparser

2018-05-13 Thread R. David Murray
R. David Murray added the comment: These are actually reasonable requests, and in fact have been brought up before and implemented: >>> x = >>> urlparse('http://me:myp...@example.com:800/foo;key1=value1?key2=value2#key3=value3#key4=value4') >>> x ParseResult(scheme='http', netloc='me:myp...@e

[issue33480] Improvement suggestions for urllib.parse.urlparser

2018-05-13 Thread Ivan Pozdeev
Ivan Pozdeev added the comment: Such drastic changes of uncertain usefulness are best discussed at python-ideas first. What you're really asking for seems to be to parse all "levels" at the same time. Try to think of a use case that would make that help anything practical and bring that to t

[issue33480] Improvement suggestions for urllib.parse.urlparser

2018-05-13 Thread brent s.
New submission from brent s. : Currently, a parsed urlparse() object looks (roughly) like this: urlparse('http://example.com/foo;key1=value1?key2=value2#key3=value3#key4=value4') returns: ParseResult(scheme='http', netloc='example.com', path='/foo', params='key1=value1', query='key2=value2',