[Gustavo J. A. M. Carneiro] > Plus, the names are full of redundancy. Why abspath(), joinpath(), > realpath(), splitall()? Why not instead: absolute(), join(), real(), > split() ? Remember that they are all methods of a Path class, you > don't > need to keep repeating 'path' all over the place. +1 for all of those that aren't also string methods. +0.9 for those that are string methods, although I suppose this depends on how much like a string a Path ends up like. Other than join() (covered in the __div__ discussion), split() is an interesting case, since the default split-on-whitespace (str.split) doesn't make a whole lot of sense with a Path, but split-on-pathsep (os.path.split) does. Does it make sense to be able to split a path on something else (like str.split), or should people just convert to/ from a string? Should there be a maxsplit argument? =Tony.Meyer
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4