Python for small systems (ucLinux)

[Jeffery D. Collins]

I don't think it would be too difficult to use Pippy as a starting 
point.  The
footprint reduction logic involves the heavy use of macros -- all 
settable in
config.h.  It might be easier to just check out the same version from the
python repository, diff  the src/{Python, Object, ...} directories and merge
the non-palm stuff.   I'll have to look more carefully at the code to 
get a better
idea.  If you decide to use Pippy, contact me offline with questions. 

BTW, have you tried to build python without (most of) the extension 
modules and
then use freeze to select only the necessary modules?  IIRC, you can 
even turn
off unicode support - there is a macro for this - as well as complex number
support.  You might want to try this first; it may be good enough.

Mike Meyer wrote:

>fpm at u.washington.edu (Frank Miles) writes:
>
>  
>
>>In article <b2djc9$vdp$1 at news.netpower.no>,
>>It might take a lot of work, but the project to create a Python
>>interpreter for the Palm platform might have some useful information.
>>Try:
>>	http://www.isr.uci.edu/projects/sensos/python/software.html
>>    
>>
>
>There a Python port available for Palm platforms. See <URL:
>http://pippy.sourceforge.net/ > for details. It's based on a
>stripped-down version of 1.5.2, and would probably make a better
>starting place for such a project than a real python distribution.
>
>        <mike
>  
>


-- 
Jeffery Collins (http://www.boulder.net/~jcollins)