Clarify if os.path.basename is equivalent to pathlib.Path.name

[bschubert (Brian Schubert)]

Related:

Pathlib: preserve trailing slash

I find this issue intimidating: It seems to me that we should solve it, as trailing slashes are meaningful to path resolution. Quoting man path_resolution on my local system: If a pathname ends in a ‘/’, that forces resolution of the preceding component as in Step 2: it has to exist and resolve to a directory. Otherwise, a trailing ‘/’ is ignored. (Or, equivalently, a pathname with a trailing ‘/’ is equivalent to the pathname obtained by appending ‘.’ to it.) And POSIX 4.12: A pat…

This is more a side-effect of how pathlib treats trailing slashes than anything specific to os.path.basename and Path.name. The same sort of issue pops up with e.g. os.path.dirname and Path.parent.