This is Python version 2.0.1, a bugfix release for Python 2.0=============================================================Copyright (c) 2001 Python Software Foundation.All rights reserved.Copyright (c) 2000 BeOpen.com.All rights reserved.Copyright (c) 1995-2001 Corporation for National Research Initiatives.All rights reserved.Copyright (c) 1991-1995 Stichting Mathematisch Centrum.All rights reserved.License information-------------------See the file "LICENSE" for information on the history of thissoftware, terms & conditions for usage, and a DISCLAIMER OF ALLWARRANTIES.This Python distribution contains no GNU General Public Licensed(GPLed) code so it may be used in proprietary projects just like priorPython distributions.  There are interfaces to some GNU code but theseare entirely optional.All trademarks referenced herein are property of their respectiveholders.What's new in this release?---------------------------See the file "Misc/NEWS".If you don't read instructions------------------------------Congratulations on getting this far. :-)To start building right away (on UNIX): type "./configure" in thecurrent directory and when it finishes, type "make".  The section`Build Instructions' below is still recommended reading, especiallythe part on customizing Modules/Setup.What is Python anyway?----------------------Python is an interpreted object-oriented programming language suitable(amongst other uses) for distributed application development,scripting, numeric computing and system testing.  Python is oftencompared to Tcl, Perl, Java, JavaScript, Visual Basic or Scheme.  Tofind out more about what Python can do for you, point your browser tohttp://www.python.org/.How do I learn Python?----------------------The official tutorial is still a good place to start; seehttp://www.python.org/doc/ for online and downloadable versions, aswell as a list of other introductions, and reference documentation.There's a quickly growing set of books on Python.  Seehttp://www.python.org/psa/bookstore/ for a list.Documentation-------------All documentation is provided online in a variety of formats.  Inorder of importance for new users: Tutorial, Library Reference,Language Reference, Extending & Embedding, and the Python/C API.  TheLibrary Reference is especially of immense value since much ofPython's power is described there, including the built-in data typesand functions!All documentation is also available online at the Python web site(http://www.python.org/doc/, see below).  It is available online foroccasional reference, or can be downloaded in many formats for fasteraccess.  The documentation is available in HTML, PostScript, PDF, HTMLHelp, and LaTeX formats; the LaTeX version is primarily fordocumentation authors or people with special formatting requirements.Web sites---------New Python releases and related technologies are published athttp://www.python.org/.  Come visit us!There's also a Python community web site athttp://starship.python.net/.Newsgroups and Mailing Lists----------------------------Read comp.lang.python, a high-volume discussion newsgroup aboutPython, or comp.lang.python.announce, a low-volume moderated newsgroupfor Python-related announcements.  These are also accessible asmailing lists: seehttp://www.python.org/psa/MailingLists.html for anoverview of the many Python-related mailing lists.Archives are accessible via Deja.com Usenet News: seehttp://www.deja.com/usenet.  The mailing lists are also archived, seehttp://www.python.org/psa/MailingLists.html for details.Bug reports-----------To report or search for bugs, please use the Python BugTracker athttp://sourceforge.net/bugs/?group_id=5470.Patches and contributions-------------------------To submit a patch or other contribution, please use the PythonPatch Manager athttp://sourceforge.net/patch/?group_id=5470.If you have a proposal to change Python, it's best to submit a PythonEnhancement Proposal (PEP) first.  All current PEPs, as well asguidelines for submitting a new PEP, are list athttp://python.sourceforge.net/peps/.Questions---------For help, if you can't find it in the manuals or on the web site, it'sbest to post to the comp.lang.python or the Python mailing list (seeabove).  If you specifically don't want to involve the newsgroup ormailing list, send questions to help@python.org (a group of volunteerswho answer questions as they can).  The newsgroup is the mostefficient way to ask public questions.Build instructions==================Before you can build Python, you must first configure it.  Fortunately,the configuration and build process has been streamlined for most Unixinstallations, so all you have to do is type a few commands,optionally edit one file, and sit back.  There are some platformswhere things are not quite as smooth; see the platform specific notesbelow.  If you want to build for multiple platforms sharing the samesource tree, see the section on VPATH below.You start by running the script "./configure", which determines yoursystem configuration and creates several Makefiles.  (It takes aminute or two -- please be patient!)  When it's done, you are ready torun make.  You may want to pass options to the configure script, oredit the Setup file -- see the section below on configuration optionsand variables.To build Python, you normally type "make" in the toplevel directory.This will recursively run make in each of the subdirectories: Grammar,Parser, Objects, Python and Modules, creating a library file in eachone (except Grammar).  The interpreter executable is built in the toplevel directory.  If you want or need to, you can also chdir into eachsubdirectory in turn and run make there manually (do the Modulessubdirectory last; you must use "make all sharedmods" to build thedynamically loadable modules, if you have any).Once you have built a Python interpreter, see the subsections below ontesting, configuring additional modules, and installation.  If you runinto trouble, see the next section.Troubleshooting---------------See also the platform specific notes in the next section.If recursive makes fail, try invoking make as "make MAKE=make".If you run into other trouble, see section 3 of the FAQ(http://www.python.org/cgi-bin/faqw.py orhttp://www.python.org/doc/FAQ.html) for hints on what can go wrong,and how to fix it.If you rerun the configure script with different options, remove allobject files by running "make clean" before rebuilding.  Believe it ornot, "make clean" sometimes helps to clean up other inexplicableproblems as well.  Try it before sending in a bug report!If the configure script fails or doesn't seem to find things thatshould be there, inspect the config.log file.  When you fix aconfigure problem, be sure to remove config.cache!If you get a warning for every file about the -Olimit option being nolonger supported, you can ignore it.  There's no foolproof way to knowwhether this option is needed; all we can do is test whether it isaccepted without error.  On some systems, e.g. older SGI compilers, itis essential for performance (specifically when compiling ceval.c,which has more basic blocks than the default limit of 1000).  If thewarning bothers you, edit the Makefile to remove "-Olimit 1500" fromthe OPT variable.If you get failures in test_long, or sys.maxint gets set to -1, youare probably experiencing compiler bugs, usually related tooptimization.  This is a common problem with some versions of gcc andegcs, and some vendor-supplied compilers, which can sometimes beworked around by turning off optimization.  Consider switching tostable versions (gcc 2.7.2.3, egcs 1.1.2, or contact your vendor.)From Python 2.0 onward, all Python C code is ANSI C.  Compiling usingold K&R-C-only compilers is no longer possible.  ANSI C compilers areavailable for all modern systems, either in the form of updatedcompilers from the vendor, or one of the free compilers (gcc, egcs).Platform specific notes-----------------------(Some of these may no longer apply.  If you find you can build Pythonon these platforms without the special directions mentioned here,submit a documentation bug report to SourceForge (see Bug Reportsabove) so we can remove them!)64-bit platforms: The modules audioop, imageop and rgbimg don't work.Don't try to enable them in the Modules/Setup file.  Theycontain code that is quite wordsize sensitive.  (If you have afix, let us know!)Solaris: When using Sun's C compiler with threads, at least on Solaris2.5.1, you need to add the "-mt" compiler option (the simplestway is probably to specify the compiler with this option asthe "CC" environment variable when running the configurescript).Linux:  A problem with threads and fork() was tracked down to a bug inthe pthreads code in glibc version 2.0.5; glibc version 2.0.7solves the problem.  This causes the popen2 test to fail;problem and solution reported by Pablo Bleyer.Under Linux systems using GNU libc 2 (aka libc6), the cryptmodule now needs the -lcrypt option.  Uncomment this flag inModules/Setup, or comment out the crypt module in the samefile. Most modern Linux systems use glibc2.FreeBSD 3.x and probably platforms with NCurses that use libmytinfo orsimilar: When using cursesmodule, the linking is not done inthe correct order with the defaults.  Remove "-ltermcap" fromthe readline entry in Setup, and use as curses entry: "cursescursesmodule.c -lmytinfo -lncurses -ltermcap" - "mytinfo" (socalled on FreeBSD) should be the name of the auxiliary libraryrequired on your platform.  Normally, it would be linkedautomatically, but not necessarily in the correct order.BSDI:BSDI versions before 4.1 have known problems with threads,which can cause strange errors in a number of modules (forinstance, the 'test_signal' test script will hang forever.)Turning off threads (with --with-threads=no) or upgrading toBSDI 4.1 solves this problem.DEC Unix: Run configure with --with-dec-threads, or with--with-threads=no if no threads are desired (threads are on bydefault).  When using GCC, it is possible to get an internalcompiler error if optimization is used.  This was reported forGCC 2.7.2.3 on selectmodule.c.  Manually compile the affectedfile without optimization to solve the problem.DEC Ultrix: compile with GCC to avoid bugs in the native compiler,and pass SHELL=/bin/sh5 to Make when installing.AIX:A complete overhaul of the shared library support is now inplace.  See Misc/AIX-NOTES for some notes on how it's done.(The optimizer bug reported at this place in previous releaseshas been worked around by a minimal code change.)In addition, Gary Duzan has a hint for C++ users: to enablefull C++ module support, set CC="xlC" (or CC="xlC_r" for threadsupport in AIX 4.2.1).HP-UX:Please read the file Misc/HPUX-NOTES for shared libraries.When using threading, you may have to add -D_REENTRANT to theOPT variable in the top-level Makefile; reported by Pat Knight,this seems to make a difference (at least for HP-UX 10.20)even though config.h defines it.Minix:  When using ack, use "CC=cc AR=aal RANLIB=: ./configure"!SCO:The following apply to SCO 3 only; Python builds out of the boxon SCO 5 (or so we've heard).1) Everything works much better if you add -U__STDC__ to thedefs.  This is because all the SCO header files are broken.Anything that isn't mentioned in the C standard isconditionally excluded when __STDC__ is defined.2) Due to the U.S. export restrictions, SCO broke the cryptstuff out into a separate library, libcrypt_i.a so the LIBSneeded be set to:LIBS=' -lsocket -lcrypt_i'SunOS 4.x: When using the SunPro C compiler, you may want to use the'-Xa' option instead of '-Xc', to enable some needed non-ANSISunisms.NeXT:   To build fat binaries, use the --with-next-archs switchdescribed below.QNX:Chris Herborth (chrish@qnx.com) writes:configure works best if you use GNU bash; a port is available onftp.qnx.com in /usr/free.  I used the following process to build,test and install Python 1.5.x under QNX:1) CONFIG_SHELL=/usr/local/bin/bash CC=cc RANLIB=: \    ./configure --verbose --without-gcc --with-libm=""2) copy Modules/Setup.in to Modules/Setup; edit Modules/Setup to   activate everything that makes sense for your system... tested   here at QNX with the following modules:array, audioop, binascii, cPickle, cStringIO, cmath,crypt, curses, errno, fcntl, gdbm, grp, imageop,_locale, math, md5, new, operator, parser, pcre,posix, pwd, readline, regex, reop, rgbimg, rotor,select, signal, socket, soundex, strop, struct,syslog, termios, time, timing, zlib, audioop, imageop, rgbimg3) make SHELL=/usr/local/bin/bash    or, if you feel the need for speed:      make SHELL=/usr/local/bin/bash OPT="-5 -Oil+nrt"4) make SHELL=/usr/local/bin/bash test   Using GNU readline 2.2 seems to behave strangely, but I   think that's a problem with my readline 2.2 port.  :-\5) make SHELL=/usr/local/bin/bash installIf you get SIGSEGVs while running Python (I haven't yet, butI've only run small programs and the test cases), you'reprobably running out of stack; the default 32k could be alittle tight.  To increase the stack size, edit the Makefilein the Modules directory to read: LDFLAGS = -N 48kBeOS:Chris Herborth (chrish@qnx.com) writes:See BeOS/README for notes about compiling/installing Python onBeOS R3 or later.  Note that only the PowerPC platform issupported for R3; both PowerPC and x86 are supported for R4.Cray T3E: Konrad Hinsen writes:1) Don't use gcc. It compiles Python/graminit.c into something   that the Cray assembler doesn't like. Cray's cc seems to work   fine.2) Comment out modules md5 (won't compile) and audioop (will   crash the interpreter during the test suite).If you run the test suite, two tests will fail (rotate andbinascii), but these are not the modules you'd expect to needon a Cray.SGI:SGI's standard "make" utility (/bin/make or /usr/bin/make)does not check whether a command actually changed the file itis supposed to build.  This means that whenever you say "make"it will redo the link step.  The remedy is to use SGI's muchsmarter "smake " utility (/usr/sbin/smake), or GNU make.  Ifyou set the first line of the Makefile to #!/usr/sbin/smakesmake will be invoked by make (likewise for GNU make).There is a bug in the SGI compiler's optimization that causes abus error in PyComplex_ImagAsDouble(); this has been reported tobe triggered when importing Numeric Python and may be caused atother times.  The work-around is to build Python, delete theObjects/complexobject.o file, and then recompile withoutoptimization (use "make OPT=").OS/2:   If you are running Warp3 or Warp4 and have IBM's VisualAge C/C++        compiler installed, just change into the pc\os2vacpp directory        and type NMAKE.  Threading and sockets are supported by default        in the resulting binaries of PYTHON15.DLL and PYTHON.EXE.Monterey (64-bit AIX): The current Monterey C compiler (Visual Age)        uses the OBJECT_MODE={32|64} environment variable to set the        compilation mode to either 32-bit or 64-bit (32-bit mode is        the default).  Presumably you want 64-bit compilation mode for        this 64-bit OS.  As a result you must first set OBJECT_MODE=64        in your environment before configuring (./configure) or        building (make) Python on Monterey.Reliant UNIX: The thread support does not compile on Reliant UNIX, and        there is a (minor) problem in the configure script for that        platform as well.  This should be resolved in time for a        future release.Configuring threads-------------------As of Python 2.0, threads are enabled by default.  If you wish tocompile without threads, or if your thread support is broken, pass the--with-threads=no switch to configure.  Unfortunately, on someplatforms, additional compiler and/or linker options are required forthreads to work properly.  Below is a table of those options,collected by Bill Janssen.  We would love to automate this processmore, but the information below is not enough to write a patch for theconfigure.in file, so manual intervention is required.  If you patchthe configure.in file and are confident that the patch works, pleasesend in the patch.  (Don't bother patching the configure script itself-- it is regenerated each the configure.in file changes.)Compiler switches for threads.............................    OS/Compiler/threads                     Switches for use with threads    (POSIX is draft 10, DCE is draft 4)     (1) compile only (2) compile & link    SunOS 5.{1-5}/{gcc,SunPro cc}/solaris   (1) -D_REENTRANT   (2) -mt    SunOS 5.5/{gcc,SunPro cc}/POSIX         (1) -D_REENTRANT    DEC OSF/1 3.x/cc/DCE                    (1) -D_REENTRANT   (2) -threads     (butenhof@zko.dec.com)    Digital UNIX 4.x/cc/DCE                 (1) -D_REENTRANT   (2) -threads     (butenhof@zko.dec.com)    Digital UNIX 4.x/cc/POSIX               (1) -D_REENTRANT   (2) -pthread     (butenhof@zko.dec.com)    AIX 4.1.4/cc_r/d7                       (nothing)                           (buhrt@iquest.net)    AIX 4.1.4/cc_r4/DCE                     (nothing)                           (buhrt@iquest.net)    IRIX 6.2/cc/POSIX                       (nothing)                           (robertl@cwi.nl)Linker (ld) libraries and flags for threads...........................................    OS/threads                          Libraries/switches for use with threads    SunOS 5.{1-5}/solaris               -lthread    SunOS 5.5/POSIX                     -lpthread    DEC OSF/1 3.x/DCE                   -lpthreads -lmach -lc_r -lc         (butenhof@zko.dec.com)    Digital UNIX 4.x/DCE                -lpthreads -lpthread -lmach -lexc -lc    (butenhof@zko.dec.com)    Digital UNIX 4.x/POSIX              -lpthread -lmach -lexc -lc          (butenhof@zko.dec.com)    AIX 4.1.4/{draft7,DCE}              (nothing)                           (buhrt@iquest.net)    IRIX 6.2/POSIX                      -lpthread                           (jph@emilia.engr.sgi.com)Configuring additional built-in modules---------------------------------------You can configure the interpreter to contain fewer or more built-inmodules by editing the Modules/Setup file.  This file is initiallycopied (when the toplevel Makefile makes Modules/Makefile for thefirst time) from Setup.in; if it does not exist yet, make a copyyourself.  Never edit Setup.in -- always edit Setup.  Read thecomments in the file for information on what kind of edits areallowed.  When you have edited Setup, Makefile and config.c in theModules directory, the interpreter will automatically be rebuilt thenext time you run make in the toplevel directory.  (When workinginside the Modules directory, use "make Makefile; make".)The default collection of modules should build on any Unix system, butmany optional modules should work on all modern Unices (e.g. tryaudioop, imageop, crypt, dbm, gdbm, nis, resource, termios, timing,syslog, _curses, pyexpat, readline, rgbimg, zlib).  Often the quickestway to determine whether a particular module works or not is to see ifit will build: enable it in Setup, then if you get compilation or linkerrors, disable it -- you're missing support.On SGI IRIX, there are modules that interface to many SGI specificsystem libraries, e.g. the GL library and the audio hardware.For SunOS and Solaris, enable module "sunaudiodev" to support theaudio device. Likewise, for Linux systems, enable "linuxaudiodev".In addition to the file Setup, you can also edit the file Setup.local.(the makesetup script processes both).  You may find it moreconvenient to edit Setup.local and leave Setup alone.  Then, wheninstalling a new Python version, you can copy your old Setup.localfile.Setting the optimization/debugging options------------------------------------------If you want or need to change the optimization/debugging options forthe C compiler, assign to the OPT variable on the toplevel makecommand; e.g. "make OPT=-g" will build a debugging version of Pythonon most platforms.  The default is OPT=-O; a value for OPT in theenvironment when the configure script is run overrides this default(likewise for CC; and the initial value for LIBS is used as the baseset of libraries to link with).Testing-------To test the interpreter, type "make test" in the top-level directory.This runs the test set twice (once with no compiled files, once withthe compiled files left by the previous test run).  The test setproduces some output.  You can generally ignore the messages aboutskipped tests due to optional features which can't be imported.  (Ifyou want to test those modules, edit Modules/Setup to configure them.)If a message is printed about a failed test or a traceback or coredump is produced, something is wrong.  On some Linux systems (thosethat are not yet using glibc 6), test_strftime fails due to anon-standard implementation of strftime() in the C library. Pleaseignore this, or upgrade to glibc version 6.IMPORTANT: If the tests fail and you decide to mail a bug report,*don't* include the output of "make test".  It is useless.  Run thefailing test manually, as follows:python ../Lib/test/test_whatever.py(substituting the top of the source tree for .. if you built in adifferent directory).  This runs the test in verbose mode.Installing----------To install the Python binary, library modules, shared library modules(see below), include files, configuration files, and the manual page,just typemake installThis will install all platform-independent files in subdirectories ofthe directory given with the --prefix option to configure or to the`prefix' Make variable (default /usr/local).  All binary and otherplatform-specific files will be installed in subdirectories if thedirectory given by --exec-prefix or the `exec_prefix' Make variable(defaults to the --prefix directory) is given.All subdirectories created will have Python's version number in theirname, e.g. the library modules are installed in"/usr/local/lib/python<version>/" by default, where <version> is the<major>.<minor> release number (i.e. "2.0", even though this is Python2.0.1).  The Python binary is installed as "python<version>" and ahard link named "python" is created.  The only file not installed witha version number in its name is the manual page, installed as"/usr/local/man/man1/python.1" by default.If you have a previous installation of a pre-2.0 Python that you don'twant to replace yet, usemake altinstallThis installs the same set of files as "make install" except itdoesn't create the hard link to "python<version>" named "python" andit doesn't install the manual page at all.The only thing you may have to install manually is the Python mode forEmacs found in Misc/python-mode.el.  (But then again, more recentversions of Emacs may already have it.)  Follow the instructions thatcame with Emacs for installation of site-specific files.Configuration options and variables-----------------------------------Some special cases are handled by passing options to the configurescript.WARNING: if you rerun the configure script with different options, youmust run "make clean" before rebuilding.  Exceptions to this rule:after changing --prefix or --exec-prefix, all you need to do is removeModules/getpath.o.--with(out)-gcc: The configure script uses gcc (the GNU C compiler) ifit finds it.  If you don't want this, or if this compiler isinstalled but broken on your platform, pass the option--without-gcc.  You can also pass "CC=cc" (or whatever thename of the proper C compiler is) in the environment, but theadvantage of using --without-gcc is that this option isremembered by the config.status script for its --recheckoption.--prefix, --exec-prefix: If you want to install the binaries and thePython library somewhere else than in /usr/local/{bin,lib},you can pass the option --prefix=DIRECTORY; the interpreterbinary will be installed as DIRECTORY/bin/python and thelibrary files as DIRECTORY/lib/python/*.  If you pass--exec-prefix=DIRECTORY (as well) this overrides theinstallation prefix for architecture-dependent files (like theinterpreter binary).  Note that --prefix=DIRECTORY alsoaffects the default module search path (sys.path), whenModules/config.c is compiled.  Passing make the optionprefix=DIRECTORY (and/or exec_prefix=DIRECTORY) overrides theprefix set at configuration time; this may be more convenientthan re-running the configure script if you change your mindabout the install prefix.--with-readline: This option is no longer supported.  To use GNUreadline, enable module "readline" in the Modules/Setup file.--with-threads: On most Unix systems, you can now use multiplethreads, and support for this is enabled by default.  Todisable this, pass --with-threads=no.  If the library requiredfor threads lives in a peculiar place, you can use--with-thread=DIRECTORY.  IMPORTANT: run "make clean" afterchanging (either enabling or disabling) this option, or youwill get link errors!  Note: for DEC Unix use--with-dec-threads instead.--with-sgi-dl: On SGI IRIX 4, dynamic loading of extension modules issupported by the "dl" library by Jack Jansen, which isftp'able from ftp://ftp.cwi.nl/pub/dynload/dl-1.6.tar.Z.This is enabled (after you've ftp'ed and compiled the dllibrary) by passing --with-sgi-dl=DIRECTORY where DIRECTORYis the absolute pathname of the dl library.  (Don't bother onIRIX 5, it already has dynamic linking using SunOS styleshared libraries.)  Support for this feature is deprecated.--with-dl-dld: Dynamic loading of modules is rumored to be supportedon some other systems: VAX (Ultrix), Sun3 (SunOS 3.4), SequentSymmetry (Dynix), and Atari ST.  This is done using acombination of the GNU dynamic loading package(ftp://ftp.cwi.nl/pub/dynload/dl-dld-1.1.tar.Z) and anemulation of the SGI dl library mentioned above (the emulationcan be found atftp://ftp.cwi.nl/pub/dynload/dld-3.2.3.tar.Z).  Toenable this, ftp and compile both libraries, then call configure, passing it the option--with-dl-dld=DL_DIRECTORY,DLD_DIRECTORY where DL_DIRECTORY isthe absolute pathname of the dl emulation library andDLD_DIRECTORY is the absolute pathname of the GNU dld library.(Don't bother on SunOS 4 or 5, they already have dynamiclinking using shared libraries.)  Support for this feature isdeprecated.--with-libm, --with-libc: It is possible to specify alternativeversions for the Math library (default -lm) and the C library(default the empty string) using the options--with-libm=STRING and --with-libc=STRING, respectively.  Forexample, if your system requires that you pass -lc_s to the Ccompiler to use the shared C library, you can pass--with-libc=-lc_s. These libraries are passed after all otherlibraries, the C library last.--with-next-archs='arch1 arch2': Under NEXTSTEP, this will buildall compiled binaries with the architectures listed.  This willalso correctly set the target architecture-specific resourcedirectory.  (This option is not supported on other platforms.)--with-libs='libs': Add 'libs' to the LIBS that the python interpreteris linked against.Building for multiple architectures (using the VPATH feature)-------------------------------------------------------------If your file system is shared between multiple architectures, itusually is not necessary to make copies of the sources for eacharchitecture you want to support.  If the make program supports theVPATH feature, you can create an empty build directory for eacharchitecture, and in each directory run the configure script (on theappropriate machine with the appropriate options).  This creates thenecessary subdirectories and the Makefiles therein.  The Makefilescontain a line VPATH=... which points to a directory containing theactual sources.  (On SGI systems, use "smake -J1" instead of "make" ifyou use VPATH -- don't try gnumake.)For example, the following is all you need to build a minimal Pythonin /usr/tmp/python (assuming ~guido/src/python is the topleveldirectory and you want to build in /usr/tmp/python):$ mkdir /usr/tmp/python$ cd /usr/tmp/python$ ~guido/src/python/configure[...]$ make[...]$Note that Modules/Makefile copies the original Setup file to the builddirectory if it finds no Setup file there.  This means that you canedit the Setup file for each architecture independently.  For thisreason, subsequent changes to the original Setup file are not trackedautomatically, as they might overwrite local changes.  To force a copyof a changed original Setup file, delete the target Setup file.  (Themakesetup script supports multiple input files, so if you want to befancy you can change the rules to create an empty Setup.local if itdoesn't exist and run it with arguments $(srcdir)/Setup Setup.local;however this assumes that you only need to add modules.)Building on non-UNIX systems----------------------------For Windows (2000/NT/ME/98/95), assuming you have MS VC++ 6.0, theproject files are in PCbuild, the workspace is pcbuild.dsw.  SeePCbuild\readme.txt for detailed instructions.For other non-Unix Windows compilers, in particular Windows 3.1 andfor OS/2, enter the directory "PC" and read the file "readme.txt".For the Mac, a separate source distribution will be made available,for use with the CodeWarrior compiler.  If you are interested in Macdevelopment, join the PythonMac Special Interest Group(http://www.python.org/sigs/pythonmac-sig/, or send email topythonmac-sig-request@python.org).Of course, there are also binary distributions available for theseplatforms -- seehttp://www.python.org/.To port Python to a new non-UNIX system, you will have to fake theeffect of running the configure script manually (for Mac and PC, thishas already been done for you).  A good start is to copy the fileconfig.h.in to config.h and edit the latter to reflect the actualconfiguration of your system.  Most symbols must simply be defined as1 only if the corresponding feature is present and can be left aloneotherwise; however the *_t type symbols must be defined as some variantof int if they need to be defined at all.Miscellaneous issues====================Emacs mode----------There's an excellent Emacs editing mode for Python code; see the fileMisc/python-mode.el.  Originally written by the famous Tim Peters, itis now maintained by the equally famous Barry Warsaw (it's nocoincidence that they now both work on the same team).  The latestversion, along with various other contributed Python-related Emacsgoodies, is online athttp://www.python.org/emacs/python-mode.  Andif you are planning to edit the Python C code, please pick up thelatest version of CC Modehttp://www.python.org/emacs/cc-mode; itcontains a "python" style used throughout most of the Python C sourcefiles.  (Newer versions of Emacs or XEmacs may already come with thelatest version of python-mode.)The Tk interface----------------Tk (the user interface component of John Ousterhout's Tcl language) isalso usable from Python.  Since this requires that you first build andinstall Tcl/Tk, the Tk interface is not enabled by default whenbuilding Python from source.  Python supports Tcl/Tk version 8.0 andhigher.Seehttp://dev.ajubasolutions.com/ for more info on Tcl/Tk, includingthe on-line manual pages.To enable the Python/Tk interface, once you've built and installedTcl/Tk, load the file Modules/Setup into your favorite text editor andsearch for the string "_tkinter".  Then follow the instructions foundthere.  If you have installed Tcl/Tk or X11 in unusual places, youwill have to edit the first line to fix or add the -I and -L options.(Also see the general instructions at the top of that file.)For more Tkinter information, see the Tkinter Resource page:http://www.python.org/topics/tkinter/There are demos in the Demo/tkinter directory, in the subdirectoriesguido, matt and www (the matt and guido subdirectories have beenoverhauled to use more recent Tkinter coding conventions).Note that there's a Python module called "Tkinter" (capital T) whichlives in Lib/lib-tk/Tkinter.py, and a C module called "_tkinter"(lower case t and leading underscore) which lives inModules/_tkinter.c.  Demos and normal Tk applications import only thePython Tkinter module -- the latter uses the C _tkinter moduledirectly.  In order to find the C _tkinter module, it must be compiledand linked into the Python interpreter -- the _tkinter line in theSetup file does this.  In order to find the Python Tkinter module,sys.path must be set correctly -- the TKPATH assignment in the Setupfile takes care of this, but only if you install Python properly("make install libinstall").  (You can also use dynamic loading forthe C _tkinter module, in which case you must manually fix up sys.pathor set $PYTHONPATH for the Python Tkinter module.)Distribution structure----------------------Most subdirectories have their own README files.  Most files havecomments..cvsignoreAdditional filename matching patterns for CVS to ignoreBeOS/Files specific to the BeOS portDemo/           Demonstration scripts, modules and programsDoc/Documentation sources (LaTeX)Grammar/        Input for the parser generatorInclude/        Public header filesLICENSELicensing informationLib/            Python library modulesMakefile.in     Source from which config.status creates the MakefileMisc/           Miscellaneous useful filesModules/        Implementation of most built-in modulesObjects/        Implementation of most built-in object typesPC/             Files specific to PC ports (DOS, Windows, OS/2)PCbuild/Build directory for Microsoft Visual C++Parser/         The parser and tokenizer and their input handlingPython/         The byte-compiler and interpreterREADME          The file you're reading nowTools/          Some useful programs written in Pythonacconfig.h      Additional input for the GNU autoheader programconfig.h.in     Source from which config.h is created (GNU autoheader output)configure       Configuration shell script (GNU autoconf output)configure.in    Configuration specification (input for GNU autoconf)install-sh      Shell script used to install filesThe following files will (may) be created in the toplevel directory bythe configuration and build processes:Makefile        Build rulesbuildnoKeeps track of the build numberconfig.cache    Cache of configuration variablesconfig.h        Configuration headerconfig.log      Log from last configure runconfig.status   Status from last run of the configure scriptgetbuildinfo.oObject file from Modules/getbuildinfo.clibpython<version>.aThe library archivepython          The executable interpretertags, TAGS      Tags files for vi and EmacsThat's all, folks!--------------------Guido van Rossum (home page:http://www.python.org/~guido/)