homepage

urlunparse(url or params = bytes object) produces a result
with the repr of the bytes object.
urllib.parse.urlunparse(['http', 'host', '/dir', b'params', '', ''])
--> "http://host/dir;b'params'"
That's confusing since urllib/parse.py goes to a lot of trouble to
support both bytes and str. Simplest fix is to only accept str:
Index: Lib/urllib/parse.py
@@ -219,5 +219,5 @@ def urlunparse(components):
 scheme, netloc, url, params, query, fragment = components
 if params:
- url = "%s;%s" % (url, params)
+ url = ';'.join((url, params))
 return urlunsplit((scheme, netloc, url, query, fragment))
 
Some people at comp.lang.python tell me code shouldn't anyway do str()
just in case it is needed like urllib does, not that I can make much
sense of that discussion. (Subject: harmful str(bytes)).
BTW, the str vs bytes code doesn't have to be quite as painful as in
urllib.parse, I enclose patch which just rearranges and factors out
some code.

I believe this is effectively a duplicate of issue 9873. If not, it is still probably more appropriate to add commentary there rather than have a separate bug here.