Description
problem description
The semantics of what url.join does depends on the value of the input parameter. this is bad.
for example you may want to join in a path after a base url. If that path contains a ":" at the wrong spot this overwrites the entire url because it gets interpreted as a protocol specifier.
Very stringly typed, kinda reminds me of building sql queries from concatenating strings, and very much does not lead the developer down a "pit of success".
proposed solution
deprecate the join api.
introduce .replace_x and, where applicable, .extend_x for x in [scheme, host, port, path, "file" (last part of the path), query, fragment, username, password]
with clear documentation, especially for the path part, on what extending does (straight string append, dependency on leading slashes, interaction with the "file" part, etc.), or splitting the extend function into multiple clearly defined ones.
reasoning
path handling is hard and a big source of security issues. it should be solved in the common dependency instead of by each individual aplication.
i am willing to contribute the required code.