Furthermore, urlparse is almost always the wrong choice for the job. It parses path parameters (not to be confused with IRL parameters aka query string), which

Furthermore, urlparse is almost always the wrong choice for the job. It parses path parameters (not to be confused with IRL parameters aka query string), which is why it splits in semicolon in the first place, an obsolete practice that I don’t even remember when’s the last time I found make sense. urlsplit is both more correct and does not have the bug/vulnerability to begin with.