[issue2786] Names in traceback should have class names, if they're methods

New submission from Matthias Urlichs <[EMAIL PROTECTED]>: Consider this simple error: >>> class foo(object): ... def __init__(self,bar): ...pass ... >>> foo() Traceback (most recent call last): File "", line 1, in TypeError: __init__() takes exactly 2 positional arguments (1 given) >>>

[issue2786] Names in traceback should have class names, if they're methods

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: This is similar to issue2516. -- nosy: +belopolsky __ Tracker <[EMAIL PROTECTED]> __ ___

[issue2786] Names in traceback should have class names, if they're methods

Changes by Terry J. Reedy : -- versions: +Python 3.2 -Python 2.6, Python 3.0 ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue2786] Names in traceback should have class names, if they're methods

Changes by Georg Brandl <[EMAIL PROTECTED]>: -- components: +Interpreter Core priority: -> low type: behavior -> feature request versions: +Python 2.6, Python 3.0 __ Tracker <[EMAIL PROTECTED]> _

[issue2786] Names in traceback should have class names, if they're methods

Ezio Melotti added the comment: Perhaps __qualname__ could be used in the traceback. -- keywords: +easy nosy: +ezio.melotti, pitrou stage: -> needs patch versions: +Python 3.4 -Python 3.2 ___ Python tracker ___

[issue2786] Names in traceback should have class names, if they're methods

Illia Polosukhin added the comment: Talked with David Murray (r.david.murray) at @pycon2013 sprints - will try to address this. -- nosy: +ilblackdragon ___ Python tracker ___ ___

[issue2786] Names in traceback should have class names, if they're methods

Illia Polosukhin added the comment: The issue is not that easy to address - because PyFunctionObject is not available from PyEval_EvalCodeEx. Another note, is that the issue of reporting only function name without class name is observed in many places, not just for example above. Still, will