Downloads as of 7/12/04:
To install the Python 2.3.4 binary files on Windows/CE just unzip the Python 2.3.4 binaries for Pocket PC 2003 or Python 2.3.4 binaries for Pocket PC 2002 into the "\Program Files\Python\Lib" directory on the Pocket PC device.
If you want to be able to double-click on Python files and have them execute, you will need to add registry entries on the Pocket PC. Using the Pocket PC file explorer, go to the "\Program Files\Python\Lib" directory on the Pocket PC and double click on the "Setup Registry" icon. It will setup the registry on your Pocket PC to allow for double clicking on ".py" and ".pyc" files.
It is now possible to execute a user Python file on interactive startup. If the file "\Temp\pythonrc.py" exists, it is executed before the interactive shell is started.
To install the Tkinter binary files on Windows/CE just unzip Tkinter binaries into the top-level directory on the Pocket PC device. Note that the TCL/TK files are put in a place where no changes to the Windows/CE registry are required.
Here are the sources required to compile Python 2.3.4 for Windows/CE. This is a directory hierarchy overlay to the Python-2.3.4 distribution source hierarchy. It should be obvious where things match up -- where the Modules, PC, PCbuild and Python directories live. Once this hierarchy is copied over the Python 2.3.4 distribution you can go to the PCbuild/WinCE directory and do an "nmake" to build Python 2.3.4 for Windows/CE. There is a sample file (WCEARM.BAT) file to set up the compilation environment for ARM using Embedded Visual C++ 4.0 and the Pocket PC 2003 SDK (wcearm300.bat does the same for Visual C++ 3.0 and the Pocket PC 2002 SDK). The default build is ARMREL (StrongARM Release). To get a debug build do "nmake CFG=ARMDEB". It is the case that the Embedded Visual C++ IDE has a problem debugging projects that are built entirely out of an external makefile (it crashes) so there is a small project in the directory (python.vcp) that you can use the build a debug Python.exe that is, in fact, debuggable using the IDE.
If you want to build PyWin32, you need to get the source distribution zip file from SourceForge. You can then set the environment variable PYWIN32ROOT to be the root of the PyWin32 source hierarchy. Doing an "nmake all" from the Python PCbuild/WinCE directory will cause the PyWin32 modules to be built (by default they are not built).
As you might expect, there are no warrantees (implied or otherwise) for this software. Use it at your own risk.
David Kashtan, Validus Medical Systems Inc.