From 003091cd51c5278e3ef76b6db01bd719b8b1c416 Mon Sep 17 00:00:00 2001 From: "Kurt B. Kaiser" Date: Mon, 17 Feb 2003 18:57:16 +0000 Subject: M NEWS.txt M PyShell.py M ScriptBinding.py M rpc.py M run.py Clean up the way IDLEfork handles termination of the subprocess, restore ability to interrupt user code in Windows (so long as it's doing terminal I/O). 1. Handle subprocess interrupts in Windows with an RPC message. 2. Run/F5 will restart the subprocess even if user code is running. 3. Restart the subprocess if the link is dropped. 4. Exit IDLE cleanly even during I/O. 4. In rpc.py, remove explicit calls to statelock, let the condition variable handle acquire() and release(). --- Lib/idlelib/ScriptBinding.py | 3 --- 1 file changed, 3 deletions(-) (limited to 'Lib/idlelib/ScriptBinding.py') diff --git a/Lib/idlelib/ScriptBinding.py b/Lib/idlelib/ScriptBinding.py index 0f4483278e..9604cb8618 100644 --- a/Lib/idlelib/ScriptBinding.py +++ b/Lib/idlelib/ScriptBinding.py @@ -124,9 +124,6 @@ class ScriptBinding: flist = self.editwin.flist shell = flist.open_shell() interp = shell.interp - if interp.tkconsole.executing: - interp.display_executing_dialog() - return interp.restart_subprocess() # XXX Too often this discards arguments the user just set... interp.runcommand("""if 1: -- cgit v1.2.1