➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2016-07-25 17:29 by Al.Sweigart, last changed 2022-04-11 14:58 by admin. 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) *  |
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 |
| 2022-04-11 14:58:34 | admin | set | github: 71802 |
| 2016-07-25 19:43:10 | terry.reedy | set | status: open -> closed superseder: IDLE - debugger steps into print and over rpc.py code messages: + msg271303 resolution: duplicate stage: resolved |
| 2016-07-25 17:29:19 | Al.Sweigart | create | |