On 2021-01-06 at 07:07:30 +0300, Mikhail V wrote:

I'd like to have an option to force the path separator for the "os.path.join()" method. E.g. if I run the script on Windows, but I generate, say, an URL, I'd find it convenient to use the same method, but with an explicit flag to "join" with the forward slash (because URLs use it). Currently I simply use an f-string to combine a path, like e.g.:

path = f"{root}/{dir}"

but it will insert extra "/" if there if "root" already has "/" on the end. But the "join" method will not, which is a pro for the method vs "manual" string construct.

I know there is the "pathlib" module with all conversion methods, but it's overkill for many tasks. So I'd rather like to have an option to write for example:

path = os.path.join (root, dir, sep = "posix")

So that it joins with the forward slash even if run on Windows. Also it seems that e.g. "os.path.split()" already supports both separators, so I think this addition won't bring inconsistency into the module and its usage.

I'm not sure whether a method in the os module should understand URLs (are URLs part of the OS, or part of something else?), but in any case, in your example, it would make more sense to have a "URL" separator and not use "posix" as a simple synonym for forward slash. IMO, using "/" itself is clearer. That said, AIUI, there's nothing stopping a web server from using whatever separators it wants. Everything after the domain name is up to the web server to interpret; it just happens that most early web servers ran on Unix/Posix/Linux boxes and mapped URLs fairly directly to parts of the file system, and "/" was more natural than anything else.

On 2021-01-05 20:07, Mikhail V wrote:

I'd like to have an option to force the path separator for the "os.path.join()" method.

The urljoin method was made for the URL use case: from urllib.parse import urljoin urljoin('http://www.cwi.nl/%7Eguido/Python.html', 'FAQ.html') 'http://www.cwi.nl/%7Eguido/FAQ.html' From: https://docs.python.org/3/library/urllib.parse.html#urllib.parse.urljoin -Mike

On Wed, Jan 06, 2021 at 07:07:30AM +0300, Mikhail V wrote:

I'd like to have an option to force the path separator for the "os.path.join()" method. E.g. if I run the script on Windows, but I generate, say, an URL, I'd find it convenient to use the same method, but with an explicit flag to "join" with the forward slash (because URLs use it).

"I don't care about correctness, I want to add arbitrary functionality to unrelated functions because it's convenient." *wink* The whole point of using os.path.join is that you don't care what the separator is, so long as it is correct *for the OS at runtime*. But for URLs, the separator never depends on the runtime OS. It is either fixed, or at worst will depend on the protocol. URLs are also a lot more complicated than file paths, so you should be using urllib to assemble the parts: https://docs.python.org/3/library/urllib.parse.html If you can't be bothered (and let's be honest, we've all been there) there's nothing wrong with assembling URL path components with pure string operations. All you need is a one-liner: def join(*parts, sep='/'): return sep.join([part.strip(sep) for part in parts]) -- Steve

06.01.21 06:07, Mikhail V пише:

I know there is the "pathlib" module with all conversion methods, but it's overkill for many tasks. So I'd rather like to have an option to write for example:

path = os.path.join (root, dir, sep = "posix")

So that it joins with the forward slash even if run on Windows. Also it seems that e.g. "os.path.split()" already supports both separators, so I think this addition won't bring inconsistency into the module and its usage.

Use posixpath.