diff options
author | Kurt B. Kaiser <kbk@shore.net> | 2002-12-31 17:56:18 (GMT) |
---|---|---|
committer | Kurt B. Kaiser <kbk@shore.net> | 2002-12-31 17:56:18 (GMT) |
commit | f5934dd5f83af0bf5a1a41a2be31cd2ee64bfe23 (patch) | |
tree | 06862738fd1de841df4d8a938e48b1f39f022b5d /Lib | |
parent | f970d61c92fa609b97c36ad991de4cf18b062b6a (diff) | |
download | cpython-f5934dd5f83af0bf5a1a41a2be31cd2ee64bfe23.zip cpython-f5934dd5f83af0bf5a1a41a2be31cd2ee64bfe23.tar.gz cpython-f5934dd5f83af0bf5a1a41a2be31cd2ee64bfe23.tar.bz2 |
Update for Alpha 0 Release
Diffstat (limited to 'Lib')
-rw-r--r-- | Lib/idlelib/INSTALL.txt | 71 | ||||
-rw-r--r-- | Lib/idlelib/README.txt | 172 |
2 files changed, 61 insertions, 182 deletions
diff --git a/Lib/idlelib/INSTALL.txt b/Lib/idlelib/INSTALL.txt index ac05a0a..df4a0d9 100644 --- a/Lib/idlelib/INSTALL.txt +++ b/Lib/idlelib/INSTALL.txt @@ -1,58 +1,39 @@ -IDLEfork INSTALL notes -====================== +IDLEfork Installation 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. +IDLEfork requires Python Version 2.2 or later. -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. +There are several distribution files (where xx is the subversion): -See README.txt and NEWS.txt for more details on this version of IDLEfork. +IDLEfork-0.9xx.win32.exe + This is a Windows installer which will install IDLEfork in + ..../site-packages/idleforklib/ and place the idefork startup script + at ..../scripts/idlefork. Rename this to idlefork.pyw and + point your launcher icons at it. Installation is as idlefork + to avoid conflict with the original Python IDLE. +IDLEfork-0.9xx-1.noarch.rpm + This is an rpm which is designed to install as idleforklib in the + /usr/lib/python2.2 tree created by the Python2 rpm. It requires + python2 and python2-tkinter rpms. It installs as idlefork to avoid + conflict with Python IDLE. -INSTALLATION notes from IDLE fork 0.7.1 : -========================================= +IDLEfork-0.9xx.tar.gz + This is a distutils sdist (source) tarfile which can be used to make + installations on platforms not supported by the above files. + It is configured to install as IDLE, not IDLEfork. -IDLE Fork Installation on Linux: + Unpack in ..../Tools/, cd to the IDLEfork directory created, and + <python setup.py install> to install as IDLE. If you don't want to + step on Python IDLE, it is also possible to simply run <python idle.py> + to test in the IDLEfork source directory without installation. In this + case, IDLEfork will not be on your PATH unless you are in the source + directory. -Until the tarball is released, you must download a CVS copy. An excellent -place for it is +See README.txt for more details on this version of IDLEfork. -/usr/local/src/PythonX.X/Tools/idlefork, assuming that's where your Python -source is located. Put the correct version in for X.X . -# cd /usr/local/src/PythonX.X/Tools -Now do the CVS login and checkout: -# cvs -d:pserver:anonymous@cvs.idlefork.sourceforge.net:/cvsroot/idlefork login -Type an <enter> for the password. -# cvs -z3 -d:pserver:anonymous@cvs.idlefork.sourceforge.net:/cvsroot/idlefork \ - -d idlefork checkout idle - -The -d option to checkout puts the files in an idlefork directory, so you don't -step on "official" idle. - -# cd idlefork -# su to root - -# python setup.py install - -# echo idlelib >> /usr/local/lib/pythonX.X/site-packages/site-packages.pth - -This last is necessary so idle can find itself. I hope we can create/append -this file via setup.py at some point, but it needs to be done manually now, and -it only needs to be done once (unless you totally remove and reinstall python -itself). (Replace X.X with the correct version for your Python.) - -# exit from root - -NOTE that the above procedure will install idlefork IDLE on top of any -"official" IDLE that may be already installed. diff --git a/Lib/idlelib/README.txt b/Lib/idlelib/README.txt index 152d497..1307be4 100644 --- a/Lib/idlelib/README.txt +++ b/Lib/idlelib/README.txt @@ -2,157 +2,55 @@ 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. +DeveLopment Environment IDLE. The biggest change is to execute +Python code in a separate process, which is /restarted/ for each +Run (F5) initiated from an editor window. This enhancement of +IDLE has often been requested, and is now finally available, +complete with debugger. -As David Scherer aptly put it in the original IDLE fork README (below), +There is also a new GUI configuration manager which makes it easy +to select fonts, colors, and startup options. + +IDLEfork will be merged back into the Python distribution in the +near future (probably 2.3), replacing the current version of IDLE. + +As David Scherer aptly put it in the original IDLEfork README, "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. +keep both pieces." -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 +If you find bugs let us know about them by using the IDLEfork Bug +Tracker. See the IDLEfork home page at -http://idlefork.sourceforge.net +http://idlefork.sourceforge.net -for details on the various ways to give input to or contact the project. +for details. Patches are always appreciated at the IDLEfork Patch +Tracker. 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. -Thanks for trying IDLEfork, -Stephen M. Gava. -<elguavas@users.sourceforge.net> - - - -README from IDLE fork 0.7.1 : -============================= - -EXPERIMENTAL LOADER IDLE 2000-05-29 ------------------------------------ - - David Scherer <dscherer@cmu.edu> - -This is a modification of the CVS version of IDLE 0.5, updated as of -2000-03-09. It is alpha software and might be unstable. If it breaks, -you get to keep both pieces. - -If you have problems or suggestions, you should either contact me or -post to the list at http://www.python.org/mailman/listinfo/idle-dev -(making it clear that you are using this modified version of IDLE). - -Changes: - - The ExecBinding module, a replacement for ScriptBinding, executes - programs in a separate process, piping standard I/O through an RPC - mechanism to an OnDemandOutputWindow in IDLE. It supports executing - unnamed programs (through a temporary file). It does not yet support - debugging. - - When running programs with ExecBinding, tracebacks will be clipped - to exclude system modules. If, however, a system module calls back - into the user program, that part of the traceback will be shown. - - The OnDemandOutputWindow class has been improved. In particular, - it now supports a readline() function used to implement user input, - and a scroll_clear() operation which is used to hide the output of - a previous run by scrolling it out of the window. - - Startup behavior has been changed. By default IDLE starts up with - just a blank editor window, rather than an interactive window. Opening - a file in such a blank window replaces the (nonexistent) contents of - that window instead of creating another window. Because of the need to - have a well-known port for the ExecBinding protocol, only one copy of - IDLE can be running. Additional invocations use the RPC mechanism to - report their command line arguments to the copy already running. - - The menus have been reorganized. In particular, the excessively large - 'edit' menu has been split up into 'edit', 'format', and 'run'. - - 'Python Documentation' now works on Windows, if the win32api module is - present. - - A few key bindings have been changed: F1 now loads Python Documentation - instead of the IDLE help; shift-TAB is now a synonym for unindent. - -New modules: - ExecBinding.py Executes program through loader - loader.py Bootstraps user program - protocol.py RPC protocol - Remote.py User-process interpreter - spawn.py OS-specific code to start programs - -Files modified: - autoindent.py ( bindings tweaked ) - bindings.py ( menus reorganized ) - config.txt ( execbinding enabled ) - editorwindow.py ( new menus, fixed 'Python Documentation' ) - filelist.py ( hook for "open in same window" ) - formatparagraph.py ( bindings tweaked ) - idle.bat ( removed absolute pathname ) - idle.pyw ( weird bug due to import with same name? ) - iobinding.py ( open in same window, EOL convention ) - keydefs.py ( bindings tweaked ) - outputwindow.py ( readline, scroll_clear, etc ) - pyshell.py ( changed startup behavior ) - readme.txt ( <Recursion on file with id=1234567> ) - -IDLE 0.5 - February 2000 ------------------------- - -This is an early release of IDLE, my own attempt at a Tkinter-based -IDE for Python. - -For news about this release, see the file NEWS.txt. (For a more -detailed change log, see the file ChangeLog.) - -FEATURES - -IDLE has the following features: - -- coded in 100% pure Python, using the Tkinter GUI toolkit (i.e. Tcl/Tk) - -- cross-platform: works on Windows and Unix (on the Mac, there are -currently problems with Tcl/Tk) - -- multi-window text editor with multiple undo, Python colorizing -and many other features, e.g. smart indent and call tips - -- Python shell window (a.k.a. interactive interpreter) - -- debugger (not complete, but you can set breakpoints, view and step) - -USAGE - -The main program is in the file "idle.py"; on Unix, you should be able -to run it by typing "./idle.py" to your shell. On Windows, you can -run it by double-clicking it; you can use idle.pyw to avoid popping up -a DOS console. If you want to pass command line arguments on Windows, -use the batch file idle.bat. -Command line arguments: files passed on the command line are executed, -not opened for editing, unless you give the -e command line option. -Try "./idle.py -h" to see other command line options. +IDLEfork 0.9 Alpha 0 +-------------------------------- -IDLE requires Python 1.5.2, so it is currently only usable with a -Python 1.5.2 distribution. (An older version of IDLE is distributed -with Python 1.5.2; you can drop this version on top of it.) +Introduced the new RPC implementation, which includes a debugger. The +output of user code is to the shell, and the shell may be used to +inspect the environment after the run has finished. (In version 0.8.1 +the shell environment was separate from the environment of the user +code.) -COPYRIGHT +Introduced the configuration GUI and a new About dialog. -IDLE is covered by the standard Python copyright notice -(http://www.python.org/doc/Copyright.html). +Adapted to the Mac platform. -FEEDBACK +Multiple bug fixes and usability enhancements. -(removed, since Guido probably doesn't want complaints about my -changes) +Known issues: ---Guido van Rossum (home page: http://www.python.org/~guido/) +- Can't kill a tight loop in the Windows version: Use the Task Manager! +- Printing under Linux may be problematic. +- The debugger is pretty slow. +- RPC stack levels are not being pruned from debugger tracebacks. +- Changelog and NEWS.txt are incomplete. |