new material for 0.8.1 release

This commit is contained in:
Steven M. Gava 2001-07-21 09:50:55 +00:00
parent c925b1538a
commit 88ff736ee2
2 changed files with 30 additions and 9 deletions

View File

@ -1,5 +1,22 @@
INSTALLATION from IDLE fork 0.7.1 :
===================================
IDLEfork INSTALL notes
======================
The emphasis in IDLEfork is now for the project to be able to be run
directly from the unpacked source directory. This is to enable easy testing
of (and hacking on) IDLEfork, and will also prevent interfering with the
stable Python IDLE set up in any way.
To install IDLEfork just unpack the archive into its own directory wherever
you like. To run IDLEfork just go to the directory you unpacked IDLEfork
into and then run 'python idle.py' in an xterm under unix/linux, or
'idle.pyw' under windows 98/2000. Remember that IDLEfork 0.8.1 and greater
require python 2.1 or greater.
See README.txt and NEWS.txt for more details on this version of IDLEfork.
INSTALLATION notes from IDLE fork 0.7.1 :
=========================================
IDLE Fork Installation on Linux:

View File

@ -4,28 +4,32 @@ IDLEfork NEWS
---------------------------------------------------------
IDLEfork 0.8.1 (xx JUN 2001)
IDLEfork 0.8.1 (22 JUL 2001)
----------------------------
New tarball released as a result of the 'revitalisation' of the IDLEfork
project.
This release requires python 2.1 or better. Compatability with earlier
versions of python (especially ancient ones like 1.5x) is no longer
a priority in IDLEfork development.
This release is based on a merging of the earlier IDLE fork work with
current cvs IDLE (post IDLE version 0.8), with some minor additional
coding by Kurt B. Kaiser and Stephen M. Gava.
This release is basically functional but also contains some known
breakages, for instance with running things from the shell window, that
may well have been introduced in a hasty attempt to change IDLEfork's
previous startup behaviour.
breakages, particularly with running things from the shell window. Also
the debugger is not working, but I believe this was the case with the
previous IDLE fork release (0.7.1) as well.
This release is being made now to mark the point at which IDLEfork is
launching into a new stage of development.
IDLEfork CVS will now be branched to enable further development and
exploration of the two "execution in a remote process" patches submitted
by David Scherer (David's is currently in IDLEfork) and GvR on a branch,
while stabilisation and development of less heavyweight improvements
(like user customisation) can continue on the trunk.
by David Scherer (David's is currently in IDLEfork) and GvR, while
stabilisation and development of less heavyweight improvements (like
user customisation) can continue on the trunk.
IDLE fork 0.7.1 (15 AUG 2000)