Message154150
| Author |
ltaylor934 |
| Recipients |
ltaylor934 |
| Date |
2012年02月24日.19:47:18 |
| SpamBayes Score |
3.133462e-07 |
| Marked as misclassified |
No |
| Message-id |
<1330112839.68.0.0096879566667.issue14111@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
The attached script runs a long processing loop.
Start it in IDLE. Open the script and run it.
Press control-C. Result: message, KeyboardInterrupt with traceback message.
In shell window, turn on Debugger. Run the script.
Press control-C. Result: Restrat message shown in Python Shell. Debug Control shows no change.
Expected behavior: For keyboard interrupt, or for any uncaught exception, Debug Control should show the same information as if there was a breakpoint. For instance, the stack with line numbers, locals and globals.
Better: make a way to interrupt the program in a long loop or process, so that the programmer can tell -- live -- where the program is, and where most of the time is being used. Then use the regular buttons, Go, etc. to continue the process, possibly interrupted again.
Also: the IDLE Python Shell and Debug Control show no "running" indicator, so there is no easy way to tell if the program is still going. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年02月24日 19:47:19 | ltaylor934 | set | recipients:
+ ltaylor934 |
| 2012年02月24日 19:47:19 | ltaylor934 | set | messageid: <1330112839.68.0.0096879566667.issue14111@psf.upfronthosting.co.za> |
| 2012年02月24日 19:47:19 | ltaylor934 | link | issue14111 messages |
| 2012年02月24日 19:47:18 | ltaylor934 | create |
|