[issue15196] os.path.realpath gets confused when symlinks include '..'

Changes by R. David Murray : -- superseder: -> symlinks incorrectly resolved on Linux ___ Python tracker ___ ___ Python-bugs-list mai

[issue15196] os.path.realpath gets confused when symlinks include '..'

Ben Longbons added the comment: Yeah, this is a duplicate of issue 6975. Sorry also about the version thing. Although I can set this as closed: duplicate, I don't seem to be able to set what bug this is a duplicate of. -- resolution: -> duplicate status: open -> closed type: -> beh

[issue15196] os.path.realpath gets confused when symlinks include '..'

Antoine Pitrou added the comment: Indeed, this is pretty bad behaviour, especially for realpath(). Both abspath() and normpath() should never be called before any symlinks are resolved. Of course, fixing it as a bug means it could break existing code which relies on ".." fragments being folde

[issue15196] os.path.realpath gets confused when symlinks include '..'

R. David Murray added the comment: Is this a duplicate of issue 6975, or something different? 2.6 only gets security patches. (We use the version field to show what version we need to apply the fix to.) -- nosy: +r.david.murray versions: +Python 3.3 -Python 2.6 _

[issue15196] os.path.realpath gets confused when symlinks include '..'

New submission from Ben Longbons : I encountered this bug with the following filesystem layout project/build/bin/main-gdb.py -> ../src/main-gdb.py project/build/src -> ../src/ project/src/main-gdb.py -> ../py/main-gdb.py project/py/main-gdb.py where root/py/main-gdb.py contains import os print(