jimbo1qaz added the comment:
Then frigging change it!
--
___
Python tracker
<http://bugs.python.org/issue15348>
___
___
Python-bugs-list mailing list
Unsubscribe:
jimbo1qaz added the comment:
What's the intended behavior? stop debugging and quit the program? stop
debugging and continue freerunning? I'm using 3.3, can you make the patch stop
debugging the active running program when you c
jimbo1qaz added the comment:
Is it possible to make the X button quit the debugger if enabled?
--
___
Python tracker
<http://bugs.python.org/issue15348>
___
___
Changes by jimbo1qaz :
--
nosy: +jimbo1qaz
___
Python tracker
<http://bugs.python.org/issue15348>
___
___
Python-bugs-list mailing list
Unsubscribe:
jimbo1qaz added the comment:
I have confirmed that this happens on both 3.2 and .3, and it also happens when
you close any active debug window.
--
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/issue16
New submission from jimbo1qaz:
Open a Python file with IDLE and F5 it. Turn on debugger ([DEBUG ON]), F5 again
([DEBUG ON]), and close the debugger ([DEBUG OFF]). The shell is now completely
locked and must be closed (with a 'The program is still running, want to kill
it?
New submission from jimbo1qaz:
Have the debugger open, stopped on a breakpoint, and save the open file. The
whole thing will bomb after the save finishes. Changes are not lost, but I have
to reopen IDLE and lose history and breakpoints.
--
components: IDLE
messages: 171214
nosy
