[issue15335] IDLE - debugger steps into print and over rpc.py code

2017-10-25 Thread Terry J. Reedy
Terry J. Reedy added the comment: The debugger also steps into importlib, if one steps 'into' an import statement. Most of the time, this is a nuisance. If one is importing from one's own module, stepping over 'import mymod' is not a satisfactory way to avoid this. Perhaps we should add '(

[issue15335] IDLE - debugger steps into print and over rpc.py code

2016-07-25 Thread Terry J. Reedy
Terry J. Reedy added the comment: In #27615, which I will close as a duplicate of this, Al Sweigart wrote "Currently if the user "steps into" a print(), input(), sys.stdout.write() or other stdio-related call with the Source checkbox checked, it brings up PyShell.py. This is often confusing f

[issue15335] IDLE - debugger steps into print and over rpc.py code

2014-08-12 Thread Terry J. Reedy
Terry J. Reedy added the comment: FWIW: stepping into an import statement now steps into and for many more statements than the three for print/write. I am already aware that the debugger 'doc' needs to be expanded from "Debugger (toggle) This feature is not complete and considered experimenta

[issue15335] IDLE - debugger steps into print and over rpc.py code

2014-08-12 Thread Terry J. Reedy
Terry J. Reedy added the comment: Since there is currently no '_RPCFile' in idlelib, I presume it was the predecessor of PyShell.PseudoFile. Was it in run.py rather than PyShell.py? Stepping through print (only 1 is needed) steps through the two 'if's and 'return' statements of PyShell.Pseud