I'd say unsaved source is rare case; the more precious thing lost is the shell window - commands history and outputs. This is a problem both when you have kill IDLE itself because the executed code is stuck, and when you just want ensure a clean run - without Restart Shell functionality, you have to close and reopen IDLE, again losing shell history (one could remember to always Save As the shell window, but there's no convenient way to load it inside IDLE).
On Tue, Jun 12, 2012 at 2:58 AM, Bruce Sherwood <[email protected]>wrote: > I'm not sure I understand this issue, but I'll comment that this is > just one of many reasons why the user's file should always be saved > before a run, a feature introduced by David Scherer 12 years ago but > which may get periodically lost. > > Bruce Sherwood > > On Mon, Jun 11, 2012 at 5:54 PM, serwy <[email protected]> wrote: > > IDLE developers, > > > > In the interest of simplifying IDLE's code, I suggest that running IDLE > > *without* a subprocess be deprecated. Since 2009, IDLE could have > multiple > > instances running while using a subprocess. See > > http://bugs.python.org/issue1529142 > > > > Running without a subprocess has a flaw in that Ctrl+C from the IDLE GUI > can > > not be used to stop a program. This can be irritating to Python > beginners if > > an accidental infinite loop arises and the user's only recourse is to > > restart IDLE, losing any unsaved work in the editor windows. > > > > What are your thoughts? > > > > - Roger > > > > > > > > > > > > _______________________________________________ > > IDLE-dev mailing list > > [email protected] > > http://mail.python.org/mailman/listinfo/idle-dev > _______________________________________________ > IDLE-dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/idle-dev >
_______________________________________________ IDLE-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/idle-dev
