[issue11007] stack tracebacks should give the relevant class name

2020-11-04 Thread Irit Katriel
Change by Irit Katriel : -- versions: +Python 3.10 -Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue11007] stack tracebacks should give the relevant class name

2016-12-13 Thread Zachary Ware
Zachary Ware added the comment: __qualname__ has become a thing since this issue was opened, it may make implementation of this feature significantly easier. -- nosy: +zach.ware versions: +Python 3.7 -Python 3.5 ___ Python tracker

[issue11007] stack tracebacks should give the relevant class name

2016-12-13 Thread Camilla Montonen
Camilla Montonen added the comment: Reproduced original issue in 3.5.1. -- nosy: +Winterflower versions: +Python 3.5 -Python 3.3 ___ Python tracker ___

[issue11007] stack tracebacks should give the relevant class name

2011-03-19 Thread Skip Montanaro
Changes by Skip Montanaro s...@pobox.com: -- nosy: -skip.montanaro ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11007 ___ ___ Python-bugs-list

[issue11007] stack tracebacks should give the relevant class name

2011-03-08 Thread Terry J. Reedy
Terry J. Reedy tjre...@udel.edu added the comment: I am not sure that traceback changes should be made in bug-fix releases, though it is a moot point until a change is ready for 3.3. That said, having a bit more info in tracebacks so they can more often be understood without looking through

[issue11007] stack tracebacks should give the relevant class name

2011-01-26 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: trace.py has a hack for this: it uses gc.get_referrers() to crawl back from the code object to the encloding class. I would not trust this gc.get_referrers() though; it is probably slow, and there are even some crashers related to this

[issue11007] stack tracebacks should give the relevant class name

2011-01-25 Thread Joshua Blount
New submission from Joshua Blount he...@joshuablount.com: When I get a stack traceback, it would be very handy if the traceback gave me the relevant class name (along with all the current information). -- components: Interpreter Core messages: 127015 nosy: stickwithjosh priority:

[issue11007] stack tracebacks should give the relevant class name

2011-01-25 Thread Skip Montanaro
Skip Montanaro s...@pobox.com added the comment: Given this code: #!/usr/bin/env python class C: def bomb(self): 1/0 c = C() c.bomb() when run it produces Traceback (most recent call last): File stdin, line 8, in module File stdin, line 5, in bomb ZeroDivisionError: integer

[issue11007] stack tracebacks should give the relevant class name

2011-01-25 Thread Joshua Blount
Joshua Blount he...@joshuablount.com added the comment: Yes! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11007 ___ ___ Python-bugs-list

[issue11007] stack tracebacks should give the relevant class name

2011-01-25 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: Well, given you have the line number at which the method is defined, it is easy to know which class it belongs to. -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org

[issue11007] stack tracebacks should give the relevant class name

2011-01-25 Thread Skip Montanaro
Skip Montanaro s...@pobox.com added the comment: I'm not sure you can get there from here, certainly not in a straightforward way. The traceback formatter gets a reference to the code object (traceback - frame - code). That object has a name attribute (which is what's displayed) but it doesn't

[issue11007] stack tracebacks should give the relevant class name

2011-01-25 Thread Skip Montanaro
Skip Montanaro s...@pobox.com added the comment: I agree with Antoine, however, if you can come up with a reasonable patch which implements the desired behavior, I think it would be reasonable to add it to Python 3.3. The definition of reasonable is subject to interpretation. As I indicated in