➜
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.
Created on 2015-08-07 04:44 by markroseman, last changed 2022-04-11 14:58 by admin.
| Messages (2) | |||
|---|---|---|---|
| msg248175 - (view) | Author: Mark Roseman (markroseman) * | Date: 2015-08-07 04:44 | |
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 |
|||
| msg248218 - (view) | Author: Terry J. Reedy (terry.reedy) *  |
Date: 2015-08-07 19:39 | |
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. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:19 | admin | set | github: 69006 |
| 2020-01-07 22:14:08 | terry.reedy | set | assignee: terry.reedy title: no way to run program in debugger from edit window -> IDLE: run program in debugger from edit window nosy: - kbk, roger.serwy versions: + Python 3.9, - Python 2.7, Python 3.5, Python 3.6 |
| 2015-08-07 19:39:37 | terry.reedy | set | messages: + msg248218 |
| 2015-08-07 04:44:11 | markroseman | create | |