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.

Author roger.serwy
Recipients loewis, roger.serwy, serhiy.storchaka, terry.reedy
Date 2012-07-12.17:18:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1342113502.72.0.820398778953.issue15335@psf.upfronthosting.co.za>
In-reply-to
Content
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 to *any* "run.py" in the filename string:

        elif frame.f_code.co_filename.count('run.py'):
            return True

Or, you could check the name:

        elif frame.f_globals.get('__name__','') == 'idlelib.run':
            return True

Any additional logic for "in_rpc_code" can slow down code performance when debugging.

Another possible approach is to move the _RPCFile into rpc.py add additional methods to RPCHandler, like "get_remote_stdout_proxy".
History
Date User Action Args
2012-07-12 17:18:22roger.serwysetrecipients: + roger.serwy, loewis, terry.reedy, serhiy.storchaka
2012-07-12 17:18:22roger.serwysetmessageid: <1342113502.72.0.820398778953.issue15335@psf.upfronthosting.co.za>
2012-07-12 17:18:22roger.serwylinkissue15335 messages
2012-07-12 17:18:22roger.serwycreate