The auto-saving feature only saves the one editor window, not all of
them. It is possible to lose unsaved work in yet-to-be executed code in
other editor windows.
Presently, PyShell.py and a few other extensions have code paths to
handle running with and without the subprocess. Requiring a subprocess
would be simplify the code.
On 06/11/2012 06:58 PM, Bruce Sherwood 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
