Message348593
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, if the use of the
> corresponding character is unsafe, or if the corresponding character
> is reserved for some other interpretation within the particular URL
> scheme.
Your example:
```
>>> from urllib.parse import urlparse
>>> urlparse('http://user:pass#?[word@example.com:80/path')
ParseResult(scheme='http', netloc='user:pass', path='', params='', query='', fragment='?[word@example.com:80/path')
```
Part of the password is parsed as the URL fragment because the character `#` has a special meaning:
> The character "#" is unsafe and should
> always be encoded because it is used in World Wide Web and in other
> systems to delimit a URL from a fragment/anchor identifier that might
> follow it. |
|
Date |
User |
Action |
Args |
2019-07-29 03:30:11 | potomak | set | recipients:
+ potomak, Sean.Wang |
2019-07-29 03:30:11 | potomak | set | messageid: <1564371011.42.0.576532060564.issue37678@roundup.psfhosted.org> |
2019-07-29 03:30:11 | potomak | link | issue37678 messages |
2019-07-29 03:30:11 | potomak | create | |
|