tinyPython

[Mark Hammond]

The simplest way to trim fat (on Windows) is to simply remove entries from
config.c.  This will cut out modules you dont need.

After that, things get a little tricker - you really need to start kicking
out types to trim much size - eg, the complex type, or the float type.

There has been some work recently to port Python onto a number of embedded
systems - this has similar goals to yours, although will probably want to go
even further.  Guido has expressed support for this, and we may see some
changes for 1.6 (likely to be 12 months away).  If you want to see anything
before then, you probably need to get involved in this effort!

HTH...

Mark.

Kaweh Kazemi wrote in message <372c6b37.4637758 at news.teleweb.at>...

>has anybody experience with creating 'the smallest, possible working
>Python interpreter', with only the essential files included? not
>including any special modules your applications would need.
>
>the problem is, that Python is getting bigger and bigger (which is ok
>with me), but i just need the core language for my special purpose.
>
>would you share your experiences with me?
>
>kaweh
>
>btw: i am using NT and VisualC++ 6.0, so i can't use the standard
>'config/makefile' way of rebuilding python, but the provided PC
>special mechanism (which works really fine, btw).