[issue27615] IDLE's debugger steps into PyShell.py for calls to print() et al

[Terry J. Reedy]

Terry J. Reedy added the comment:

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.

--
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> IDLE - debugger steps into print and over rpc.py code

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue27615] IDLE's debugger steps into PyShell.py for calls to print() et al

[Al Sweigart]

New submission from Al Sweigart:

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.

--
assignee: terry.reedy
components: IDLE
messages: 271295
nosy: Al.Sweigart, terry.reedy
priority: normal
severity: normal
status: open
title: IDLE's debugger steps into PyShell.py for calls to print() et al
versions: Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com