[issue39625] Traceback needs more details

Change by Irit Katriel : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> stack tracebacks should give the relevant class name ___ Python tracker

[issue39625] Traceback needs more details

Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39625] Traceback needs more details

Ammar Askar added the comment: I don't know how common this situation is, the fact that all constructors go to __init__ here makes it a little tough in this case but normally you'd be able to tell by the function name. One potential solution might be to show which file the error came from

[issue39625] Traceback needs more details

Change by SilentGhost : -- components: +Interpreter Core nosy: +vstinner versions: +Python 3.9 -Python 3.8 ___ Python tracker ___

[issue39625] Traceback needs more details

szb512 added the comment: I think it is the "C2" class. Traceback is probably refering to that class. -- nosy: +sdcards ___ Python tracker ___

[issue39625] Traceback needs more details

New submission from Andrew Wall : I encountered a question on Stackoverflow where, unusually, a Traceback was given in full, but I couldn't diagnose the problem. It was like this: Traceback (most recent call last): File "soFailedTraceback.py", line 15, in c = C(C1("C1"), C2("C2"))