Author Paul Pinterits
Recipients Paul Pinterits
Date 2017-08-27.20:17:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1503865076.7.0.858933592926.issue31289@psf.upfronthosting.co.za>
In-reply-to
Content
The file paths displayed in exception tracebacks have their symlinks resolved. I would prefer if the "original" path could be displayed instead, because resolved symlinks result in unexpected paths in the traceback and can be quite confusing.

An example:

rawing@localhost ~> cat test_scripts/A.py
import B
B.throw()

rawing@localhost ~> cat test_scripts/B.py
def throw():
    raise ValueError

rawing@localhost ~> ln -s test_scripts test_symlink

rawing@localhost ~> python3 test_symlink/A.py
Traceback (most recent call last):
  File "test_symlink/A.py", line 2, in <module>
    B.throw()
  File "/home/rawing/test_scripts/B.py", line 2, in throw
    raise ValueError
ValueError

As you can see, even though both scripts reside in the same directory, the file paths displayed in the traceback look very different. At first glance, it looks like B is in a completely different place than A.
Furthermore, this behavior tends to trip up IDEs - PyCharm for example does not understand that test_scripts/B.py and test_symlink/B.py are the same file, so I end up having the same file opened in two different tabs.

Would it be possible to change this behavior and have "/home/rawing/test_symlink/B.py" show up in the traceback instead?
History
Date User Action Args
2017-08-27 20:17:56Paul Pinteritssetrecipients: + Paul Pinterits
2017-08-27 20:17:56Paul Pinteritssetmessageid: <1503865076.7.0.858933592926.issue31289@psf.upfronthosting.co.za>
2017-08-27 20:17:56Paul Pinteritslinkissue31289 messages
2017-08-27 20:17:56Paul Pinteritscreate