Giovanni Cappellotto added the comment:
What do you mean that urlparse act as unexpected?
I tried your example and I think urlparse's behavior is correct.
>From the RFC 1738:
> Octets must be encoded if they have no corresponding graphic
> character within the US-ASCII coded character set,
New submission from Sean Wang :
When an IPV4 URL with 'username:password' in it, and the password contains
special characters like #[]?, urlparse would act as unexcepted.
example:
urlparse('http://user:pass#?[w...@example.com:80/path')
--
components: Library (Lib)
messages: 348431
