[issue6651] Py3k's posixpath.relpath not compatible with ntpath.relpath

Brian Curtin added the comment: After thinking about this, I don't see a need for any change. Although it _looks_ like the relpath implementations aren't compatible based on their start default parameters, they do work the same. My code change isn't really necessary. All it does is rearrange

[issue6651] Py3k's posixpath.relpath not compatible with ntpath.relpath

Changes by Ezio Melotti : -- nosy: +ezio.melotti priority: -> normal stage: -> test needed ___ Python tracker ___ ___ Python-bugs-lis

[issue6651] Py3k's posixpath.relpath not compatible with ntpath.relpath

Brian Curtin added the comment: How does this patch look? For the sake of consistency it changes back to start=curdir. Then, if the `path` parameter is type bytes and the `start` parameter equals `curdir`, `start` is set to the bytes version of `curdir`. -- keywords: +patch nosy: +bri

[issue6651] Py3k's posixpath.relpath not compatible with ntpath.relpath

New submission from Erick Tryzelaar : It looks like Python 3.x's relpath isn't compatible between posixpath and ntpath. In posixpath.relpath, the start keyword defaults to None, but ntpath.relpath, the start keyword defaults to curdir. Interestingly enough, 2.6 and 2.7 have a different implement