4 The emphasis in IDLEfork is now for the project to be able to be run
5 directly from the unpacked source directory. This is to enable easy testing
6 of (and hacking on) IDLEfork, and will also prevent interfering with the
7 stable Python IDLE set up in any way.
9 To install IDLEfork just unpack the archive into its own directory wherever
10 you like. To run IDLEfork just go to the directory you unpacked IDLEfork
11 into and then run 'python idle.py' in an xterm under unix/linux, or
12 'idle.pyw' under windows 98/2000. Remember that IDLEfork 0.8.1 and greater
13 require python 2.1 or greater.
15 See README.txt and NEWS.txt for more details on this version of IDLEfork.
18 INSTALLATION notes from IDLE fork 0.7.1 :
19 =========================================
21 IDLE Fork Installation on Linux:
23 Until the tarball is released, you must download a CVS copy. An excellent
26 /usr/local/src/PythonX.X/Tools/idlefork, assuming that's where your Python
27 source is located. Put the correct version in for X.X .
29 # cd /usr/local/src/PythonX.X/Tools
31 Now do the CVS login and checkout:
33 # cvs -d:pserver:anonymous@cvs.idlefork.sourceforge.net:/cvsroot/idlefork login
35 Type an <enter> for the password.
37 # cvs -z3 -d:pserver:anonymous@cvs.idlefork.sourceforge.net:/cvsroot/idlefork \
38 -d idlefork checkout idle
40 The -d option to checkout puts the files in an idlefork directory, so you don't
41 step on "official" idle.
46 # python setup.py install
48 # echo "idle" > /usr/local/lib/pythonX.X/site-packages.pth
50 This last is necessary so idle can find itself. I hope we can create/append
51 this file via setup.py at some point, but it needs to be done manually now, and
52 it only needs to be done once (unless you totally remove and reinstall python
57 NOTE that the above procedure will install idlefork IDLE on top of any
58 "official" IDLE that may be already installed.