summaryrefslogtreecommitdiffstats
path: root/Lib/idlelib/NEWS.txt
diff options
context:
space:
mode:
authorKurt B. Kaiser <kbk@shore.net>2003-02-17 18:57:16 (GMT)
committerKurt B. Kaiser <kbk@shore.net>2003-02-17 18:57:16 (GMT)
commit003091cd51c5278e3ef76b6db01bd719b8b1c416 (patch)
treeafc0ea2b00d259d40f2eebd7beb33bd96a4b9eba /Lib/idlelib/NEWS.txt
parentf927f14edab27b128b1962314c1cf7c10be73ac5 (diff)
downloadcpython-003091cd51c5278e3ef76b6db01bd719b8b1c416.zip
cpython-003091cd51c5278e3ef76b6db01bd719b8b1c416.tar.gz
cpython-003091cd51c5278e3ef76b6db01bd719b8b1c416.tar.bz2
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().
Diffstat (limited to 'Lib/idlelib/NEWS.txt')
-rw-r--r--Lib/idlelib/NEWS.txt35
1 files changed, 26 insertions, 9 deletions
diff --git a/Lib/idlelib/NEWS.txt b/Lib/idlelib/NEWS.txt
index e1c6fc7..a0f1869 100644
--- a/Lib/idlelib/NEWS.txt
+++ b/Lib/idlelib/NEWS.txt
@@ -2,6 +2,32 @@
IDLEfork NEWS
+++++++++++++
+What's New in IDLEfork 0.9 Alpha 3?
+===================================
+
+*Release date: xx-xxx-2003*
+
+- Exit IDLE cleanly even when doing subprocess I/O
+
+- Handle subprocess interrupt in Windows with an RPC message.
+
+- Calling Run will restart the subprocess even if user code is running.
+
+- Restart the subprocess if it terminates itself. (VPython programs do that)
+
+- Support subclassing of exceptions, including in the shell, by moving the
+ exception formatting to the subprocess.
+
+- Known issues:
+
+ + Can't kill/restart a tight loop in the Windows version: add
+ I/O to the loop or use the Task Manager to kill the subprocess.
+ + Typing two Control-C in close succession when the subprocess is busy can
+ cause IDLE to lose communication with the subprocess. Please type one
+ only and wait for the exception to complete.
+ + Printing under some versions of Linux may be problematic.
+
+
What's New in IDLEfork 0.9 Alpha 2?
===================================
@@ -105,15 +131,6 @@ What's New in IDLEfork 0.9 Alpha 2?
- Modified idle, idle.py, idle.pyw to improve exception handling.
-- Known issues:
-
- + Can't kill a tight loop in the Windows version: Insert a
- ``print "*",`` in an outer loop or use the Task Manager to kill.
- + Typing two Control-C in close succession when the subprocess is busy can
- cause IDLE to lose communication with the subprocess. Please type one
- only and wait for the exception to complete.
- + Printing under some versions of Linux may be problematic.
-
What's New in IDLEfork 0.9 Alpha 1?
===================================