Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IDLE's debugger steps into PyShell.py for calls to print() et al #71802

Closed
AlSweigart mannequin opened this issue Jul 25, 2016 · 2 comments
Closed

IDLE's debugger steps into PyShell.py for calls to print() et al #71802

AlSweigart mannequin opened this issue Jul 25, 2016 · 2 comments
Assignees

Comments

@AlSweigart
Copy link
Mannequin

AlSweigart mannequin commented Jul 25, 2016

BPO 27615
Nosy @terryjreedy
Superseder
  • 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 = <Date 2016-07-25.19:43:10.465>
    created_at = <Date 2016-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 = <Date 2016-07-25.19:43:10.464>
    user = 'https://bugs.python.org/AlSweigart'

    bugs.python.org fields:

    activity = <Date 2016-07-25.19:43:10.464>
    actor = 'terry.reedy'
    assignee = 'terry.reedy'
    closed = True
    closed_date = <Date 2016-07-25.19:43:10.465>
    closer = 'terry.reedy'
    components = ['IDLE']
    creation = <Date 2016-07-25.17:29:19.131>
    creator = 'Al.Sweigart'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 27615
    keywords = []
    message_count = 2.0
    messages = ['271295', '271303']
    nosy_count = 2.0
    nosy_names = ['terry.reedy', 'Al.Sweigart']
    pr_nums = []
    priority = 'normal'
    resolution = 'duplicate'
    stage = 'resolved'
    status = 'closed'
    superseder = '15335'
    type = None
    url = 'https://bugs.python.org/issue27615'
    versions = ['Python 3.6']

    @AlSweigart
    Copy link
    Mannequin Author

    AlSweigart mannequin commented Jul 25, 2016

    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.

    @AlSweigart AlSweigart mannequin assigned terryjreedy Jul 25, 2016
    @AlSweigart AlSweigart mannequin added the topic-IDLE label Jul 25, 2016
    @terryjreedy
    Copy link
    Member

    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.

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    No branches or pull requests

    1 participant