[issue37296] pdb next vs __next__

Rick added the comment: I have no idea what program this was in, it's lost in the depths of time. I can't retain these things for over a year, too old, maybe in my twenties I would have remembered what code this was in but no longer. Can it. --

[issue37296] pdb next vs __next__

Ronald Oussoren added the comment: I agree. Without further information it is impossible to move forward. -- resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker

[issue37296] pdb next vs __next__

Irit Katriel added the comment: I think this ticket can be closed. Rick can always reopen it or create a new one if there is still an open problem. -- ___ Python tracker ___

[issue37296] pdb next vs __next__

Ronald Oussoren added the comment: Please add more information on how to reproduce the problem. The current description is not complete enough to be able to determine if there is a bug and if so where that bug is. -- nosy: +ronaldoussoren ___

[issue37296] pdb next vs __next__

Irit Katriel added the comment: Do you mean the python version? (Pdb) import sys (Pdb) sys.version '3.10.0a0 ' -- nosy: +iritkatriel ___ Python tracker ___

[issue37296] pdb next vs __next__

New submission from Rick : Don't know how to get version from pdb, Makefile says 2.7 Code runs but when debugging I get an error that an iterator has no next() function. It has got a __next__() function, and it runs, just not under pdb. If I create a spurious next() function, pdb runs, and