[issue1692664] warnings.py gets filename wrong for eval/exec

Thomas Kluyver added the comment: Thanks Guido, the new issue is #33375. -- ___ Python tracker ___

[issue1692664] warnings.py gets filename wrong for eval/exec

Guido van Rossum added the comment: I recommend opening a new issue (you can link to this one for past discussion). -- ___ Python tracker

[issue1692664] warnings.py gets filename wrong for eval/exec

Thomas Kluyver added the comment: Time for some bug archaeology! The reason given for not using frame.f_code.co_filename for warnings was that it can be wrong when the path of .pyc files changes. However, it looks like that was fixed in #1180193 (thanks for the pointer