You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bpo-15335: IDLE - debugger steps into print and over rpc.py code
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/terryjreedy'closed_at=<Date2016-07-25.19:43:10.465>created_at=<Date2016-07-25.17:29:19.131>labels= ['expert-IDLE']
title="IDLE's debugger steps into PyShell.py for calls to print() et al"updated_at=<Date2016-07-25.19:43:10.464>user='https://bugs.python.org/AlSweigart'
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.
Whether or not to step in idlelib/pyshell.py is part of the general issue of stepping into any idlelib file bpo-15335. I copied the above to that issue.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: