You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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=Nonecreated_at=<Date2015-08-07.04:44:11.214>labels= ['expert-IDLE', 'type-feature', '3.9']
title='IDLE: run program in debugger from edit window'updated_at=<Date2020-01-07.22:14:08.788>user='https://github.com/roseman'
If I have just an edit window open with my program, there's no way to run the program with the debugger visible. Should be a way to do so without going through the extra steps of opening up a shell window first
Agreed. I believe Al's menu revision suggested moving Debugger to Run. Debugger has to hook into Shell because it has to see packets moving between Shell and the execution process. Opening the debugger window currently requires that Shell already be open. Running a file opens Shell. So we need to rewrite Debugger to delay hooking into Shell unless Shell is present .. or until it is activated (by running a file). I believe this could be done by having a .connect_to_shell method that can be called either from .__init__ or the activate method.
There are several worse problems with Debugger. I think they need some consideration together, lest a patch for one issue interfere with a patch for another.
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:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: