Vajrasky Kok added the comment: Here is the patch with Windows support. I notice there is difference regarding resolving symbolic link with parent dir (linkA/..) between Posix and Windows.
On Windows, if linkY points to dirB, 'dirA\linkY\..' resolves to 'dirA' without resolving linkY first. It means, Windows resolves parent dir first before symbolic link. C:\Users\vajrasky\Code\playplay\pycode>mkdir dirA C:\Users\vajrasky\Code\playplay\pycode>mkdir dirB C:\Users\vajrasky\Code\playplay\pycode>cd dirA C:\Users\vajrasky\Code\playplay\pycode\dirA>mklink /D linkC ..\dirB symbolic link created for linkC <<===>> ..\dirB C:\Users\vajrasky\Code\playplay\pycode\dirA>cd ..\ C:\Users\vajrasky\Code\playplay\pycode>cd dirA\linkC\.. C:\Users\vajrasky\Code\playplay\pycode\dirA> But on Posix, if linkY points to dirB, 'dirA\linkY\..' resolves to 'dirB\..' then to the parent dir of dirB. It means, Posix resolves symbolic link first before parent dir. $ mkdir dirA $ mkdir dirB $ cd dirA $ ln -s ../dirB linkC $ cd .. $ ls dirA/linkC/.. dirA dirB ---------- Added file: http://bugs.python.org/file33089/add_non_strict_resolve_pathlib_v3.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19717> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
