[issue15335] IDLE - debugger steps through run.py internals

Changes by Terry J. Reedy : -- versions: +Python 3.5 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15335] IDLE - debugger steps through run.py internals

Changes by Terry J. Reedy : -- versions: +Python 2.7, Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15335] IDLE - debugger steps through run.py internals

Changes by Serhiy Storchaka : -- nosy: -serhiy.storchaka versions: +Python 3.4 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-lis

[issue15335] IDLE - debugger steps through run.py internals

Roger Serwy added the comment: > I suggest to add a decorator @Debugger.internal for all methods that the > debugger should not step into. It should set a function attribute that the > debugger then checks for. The decorator idea may work. I'll need to see how to make it work with the exist

[issue15335] IDLE - debugger steps through run.py internals

Martin v. Löwis added the comment: I suggest to add a decorator @Debugger.internal for all methods that the debugger should not step into. It should set a function attribute that the debugger then checks for. OTOH, I fail to see the problem. Stepping through the standard library may be usefu

[issue15335] IDLE - debugger steps through run.py internals

Roger Serwy added the comment: Debugger.py has a method "in_rpc_code" which ultimately prevents stepping though code from rpc.py. (Presently an external file named "rpc.py" can not be debugged using IDLE.) Adding "run.py" to the check would prevent run.py from being stepped, but it applies t

[issue15335] IDLE - debugger steps through run.py internals

New submission from Roger Serwy : The IDLE debugger steps through the internals of _RPCFile. To reproduce this bug, create a new .py file with a few print statements, enable the debugger, and then run the file. Stepping through the print statement enters into _RPCFile. -- components: