bring up to date for 0.8.1 release

Lib/idlelib/NEWS.txt

-original IDLE NEWS.txt :
-========================
-
+IDLEfork NEWS
+=============
 (For a more detailed change log, see the file ChangeLog.)
+---------------------------------------------------------
 
-----------------------------------------------------------------------
+
+IDLEfork 0.8.1 (xx JUN 2001)
+----------------------------
+New tarball released as a result of the 'revitalisation' of the IDLEfork
+project. 
+
+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.
+
+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.
+
+
+IDLE fork 0.7.1 (15 AUG 2000)
+-----------------------------
+First project tarball released.
+
+This was the first release of IDLE fork, which at this stage was a 
+combination of IDLE 0.5 and the VPython idle fork, with additional
+changes coded by David Scherer, Peter Schneider-Kamp and 
+Nicholas Riley. 
+
+
+original IDLE NEWS.txt :
+========================
 
 New in IDLE 0.5 (2/15/2000)
 -------------------------

Lib/idlelib/README.txt

+IDLEfork README
+===============
+
+IDLEfork is an official experimental fork of Python's Integrated 
+DeveLopment Environment IDLE. Worthwhile and successful changes and 
+additions will go back into the Python distribution's IDLE at some 
+later stage. There is no spanish inquisition.
+
+As David Scherer aptly put it in the original IDLE fork README (below), 
+"It is alpha software and might be unstable. If it breaks, you get to 
+keep both pieces." One of the aims of IDLEfork now is for it to be able 
+to be uncompressed into its own directory and run from there, that way  
+you can play with (or hack on) IDLEfork without any further installation, 
+and entirely separately from your stable python IDLE distribution.
+
+If you find bugs or undesired behaviour please code nifty patches and 
+submit them to the IDLEfork SourceForge patch manager, 8^) or let us 
+know about it in one of the appropriate fora. See the IDLEfork home 
+page at
+
+http://idlefork.sourceforge.net
+
+for details on the various ways to give input to or contact the project.
+
+Please see the files NEWS.txt and ChangeLog for more up to date
+information on changes in this release of IDLEfork.
+
+
+Thanks for trying IDLEfork,
+Stephen M. Gava.
+<elguavas@users.sourceforge.net>
+
+
+
 README from IDLE fork 0.7.1 :
 =============================