[issue6825] Minor documentation bug with os.path.split

Georg Brandl added the comment: Thanks, applied in r85453. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue6825] Minor documentation bug with os.path.split

Sandro Tosi added the comment: Hi Evan, all your comments make sense, so I prepared a new patch about it. I decided to go with the first option and adding a note about the possible different strings. Regards, Sandro -- versions: +Python 3.2 -Python 2.6 Added file: http://bugs.python.

[issue6825] Minor documentation bug with os.path.split

Evan Driscoll added the comment: Hah, I totally forgot about this thing. I'd suggest a change to the proposed patch. The patched version says: "In nearly all cases, ``join(head, tail)`` returns a location equivalent to *path* (the only exception being when there were multiple slashes

[issue6825] Minor documentation bug with os.path.split

Sandro Tosi added the comment: Hello, I find the proposed text change good, and so here's a patch to add that in a bit different format (sorry it's quite of a mess, but I took the occasion to wrap that paragraph to 80th column). Regards, Sandro -- keywords: +patch nosy: +sandro.tosi

[issue6825] Minor documentation bug with os.path.split

Jack Diederich added the comment: how about "an equivalent path" instead of "equal path"? The result of ntpath.join(ntpath.split(path)) should point to the same location even if it isn't literally the same string. -- nosy: +jackdied ___ Python tra

[issue6825] Minor documentation bug with os.path.split

New submission from Evan Driscoll : The documentation for os.path.split says, in part: "In nearly all cases, join(head, tail) equals path (the only exception being when there were multiple slashes separating head from tail)." But this is not quite true: that's not the *only* exception, a