Everything is in one library which offers consistency for all operations.
You can use forward slashes on Windows paths, which makes for much better readability.
You can access all the parts of a pathlib object with attributes like .stem, .suffix or .parent.
You can easily find the differences between paths with .relative_to()
You can easily build up complex paths with the / operator (no string additions).

Just off the top of my head.

[–] brucethemoose@lemmy.world 1 points 8 hours ago* (last edited 8 hours ago)

I suppose os.path is simpler? It's a string and operation.

Python is all about 'attention efficiency,' which there's something to be said for. People taking the path of least resistance (instead of eating time learning the more complex/OOP pathlib) to bang out their script where they just need to move a file or something makes sense. I'm with you here, but it makes sense.

...Also, os.path has much better Google SEO, heh.

[–] nibbler@discuss.tchncs.de 1 points 14 hours ago* (last edited 14 hours ago) (1 children)

if you don't need those, why burden the program with another dependency?

[–] Diplomjodler3@lemmy.world 2 points 14 hours ago

It's in the standard library, just like os or shutil.

[–] indepndnt@lemmy.world 5 points 19 hours ago

And what's with the string addition? Never heard of f-strings or even .format()?

[–] Gonzako@lemmy.world 10 points 22 hours ago (1 children)

Make a PR

[–] axEl7fB5@lemmy.cafe 7 points 20 hours ago

Be the change you want to see in the world.