On 6/11/2012 7:54 PM, serwy wrote:
In the interest of simplifying IDLE's code, I suggest that running IDLE *without* a subprocess be deprecated.
I have had the same thought for the same reason
Since 2009, IDLE could have multiple instances running while using a subprocess. See http://bugs.python.org/issue1529142
and the presumption that some (all?) of the reasons for -n are obsolete
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.
and with the thought that running user code and idle interface code in the process is slightly crazy, especially if not necessary.
What are your thoughts?
Is there any need left for no-subproccess on the three supported platforms? -- Terry Jan Reedy _______________________________________________ IDLE-dev mailing list [email protected] http://mail.python.org/mailman/listinfo/idle-dev
