[issue14196] Unhandled exceptions in pdb return value display

Terry J. Reedy added the comment: Batuhan, thanks for the nudge. For the record ... If __new__ were a normal instance method, then 'some_class.__new__()' would be a correct call, as 'some_class' would be passed to '__new__' as its first and perhaps only argument. But " __new__() is a

[issue14196] Unhandled exceptions in pdb return value display

Batuhan added the comment: Can't reproducible in py3 (3.8), IMHO can be closed. -- nosy: +BTaskaya ___ Python tracker ___ ___

[issue14196] Unhandled exceptions in pdb return value display

Terry J. Reedy added the comment: Georg, if you agree that Xavier's analysis is correct, we can close this as not a bug. -- nosy: +georg.brandl, terry.reedy ___ Python tracker

[issue14196] Unhandled exceptions in pdb return value display

Xavier de Gaye added the comment: I cannot reproduce the problem on python 2.7. The example runs without problem after fixing the example with the following changes: remove the call to pdb.set_trace(), the debugger is already started with a call to pdb.run() add the missing 'cls'

[issue14196] Unhandled exceptions in pdb return value display

Changes by Tshepang Lekhonkhobe tshep...@gmail.com: -- nosy: +tshepang ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14196 ___ ___

[issue14196] Unhandled exceptions in pdb return value display

New submission from Simon Chopin chopin.si...@gmail.com: This issue occurred at least in Python 2.7, I haven't checked in other versions. When stepping on a return statement, pdb calls the return value __str__() method to display it at the end of the line. Only, it doesn't handle the