classification
Title: IDLE's debugger steps into PyShell.py for calls to print() et al
Type: Stage: resolved
Components: IDLE Versions: Python 3.6
process
Status: closed Resolution: duplicate
Dependencies: Superseder: IDLE - debugger steps into print and over rpc.py code
View: 15335
Assigned To: terry.reedy Nosy List: Al.Sweigart, terry.reedy
Priority: normal Keywords:

Created on 2016-07-25 17:29 by Al.Sweigart, last changed 2016-07-25 19:43 by terry.reedy. This issue is now closed.

Messages (2)
msg271295 - (view) Author: Al Sweigart (Al.Sweigart) * Date: 2016-07-25 17:29
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 for beginner programmers (the target audience of IDLE) and most often not helpful for experienced developers who are stepping through their program. Comparing the cost/benefit, I'd be much more helpful for IDLE to not bring up PyShell.py and instead just treat every "step into" of a print()/input()/anything-that-goes-to-pyshell as a "step over" instead.
msg271303 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2016-07-25 19:43
Whether or not to step in idlelib/pyshell.py is part of the general issue of stepping into any idlelib file #15335.  I copied the above to that issue.
History
Date User Action Args
2016-07-25 19:43:10terry.reedysetstatus: open -> closed
superseder: IDLE - debugger steps into print and over rpc.py code
messages: + msg271303

resolution: duplicate
stage: resolved
2016-07-25 17:29:19Al.Sweigartcreate