Readme file for the UW Graphics Group installation of Python 2.6.2

This directory was created by:
1) Installing Python 2.6.2 from the MSI on a non-CSL machine
2) Running the installers for a number of Python add ons
   - PyReadline 1.5
   - IPython 0.9.1
   - PyWin32 (for Python 2.6)
   - Numpy 1.3.0 (for python 2.6)
   - SciPy 0.7.1 (again, 2.6 specific version)
   - MatPlotLib 98.5.3.0py26
   - PIL 1.1.6
   - PyFltk

   The MSI python installer placed the DLLs into a wierd spot:
   C:\Windows\SysWOW64 - I'm not sure if this is a 64 bit install or
   not. Also, there are 3 different "Py" DLLs - 2 I have never heard
   of: python26.dll, pythoncom26.dll, and pywintypes26.dll (the latter
   2 seem to be part of pythonwin). I placed a copy of these in the
   "root" directory. (See 6 below)

   It seems to work when copied over to another machine (module some
   issues with PYTHONHOME).

3) Downloading the source distribution into a different directory
4) Doing a Debug Build of:
   - Python
   - Pythonw
   - _socket
   - _ctypes
   - pyexpat
   - _multiprocessing
   - select
   - winsound

5) Copying over the stuff from the Python 2.6.2 directory (the debug
   build) appropriately.
   - The "Demo" directory
   - The directory that contain the source (although the old include
     directory is kept)
     Grammar, Modules, Objects, Parser, PC, PCbuild, Python
     Tools (things not in the binary dist are copied over)

6) I decided to keep the "python" style organization of placing the
   key binaries and DLLs into the "root" directory. (it places
   python.exe there - and sticks the DLLs into the system directory). 

   To be consistent, this directory now contains:
   - python26.dll, pythoncom26.dll, pythonwintypes26.dll
     (copied from the system directory)
   - the key executable binaries from PCBuild
     kill_python.exe and kill_python_d.exe (I don't know what these
     are!)
     python_d.exe and pythonw_d.exe
     python26_d.dll

   The idea is that the root directory goes into your system path,
   nothing else should need to.

7) Python puts the DLLs for its libraries into its DLLs folder, so
   these are copied from PCBuild (note: they are actually (PYD files,
   not DLLs)

8) Python puts the LIBs for its libraries into is libs folder, so all
   lib files from PCBuild are copies there

9) The start menu items are copied into the "Start Menu" folder. These
   might be handy to see how to start the IDEs. The IPython shortcuts
   are copied into the same folder.