Python only 3.7Mb pet with just the python binary and .py files
<<This is how you should install it for personal use>>

Python plus PyGtk (and dependencies) 6.5MB sfs with .py files and .pyo files (with symlinks for .pyc files) this method will give faster startup times since python will just use the pyo files without having to compile the .py file (the symlink will just make it use the pyo file and not fill up your save file or RAM with all of the pyc files)
<<this is the best method for sfs distribution including remastering the pupXXX.sfs>>

Both should be full working versions - the big difference is that when you run Python with the pet your save file will grow slightly due to the automatically generated .pyc files from .py files that are called (or .pyo if you pass the -OO flag to python) The sfs already has the .pyo files and a symlink for .pyc which Python automatically detects and uses. This is so that it doesn't have to waste time compiling the bytecode on subsequent runs.

To keep the pyc and pyo files from being generated (and save space in the pet version) you can replace the python symlink to python2.6 with a script that has something like:

I added a minimal pet with pycairo, pygobject, pygtk and pysqlite included. It includes the required py files libraries and files to build/test new python packages... the only thing that is removed is the 2to3 (python2 to python3) compatibility checks, but it is in the sfs if you really need it for development purposes.

I used the previous script to prevent them from filling up your save file.
To revert to normal operation and speed up your second run (by saving the compiled bytecode to your save file or RAM in pfix=ram mode), this will revert it to normal behavior

That would have been in the DEV folder - I can pet it when I get back home after the holidays... or you can get the include files (*.h) straight from the python source package and put them in /usr/include._________________Web Programming - Pet Packaging 100 & 101

That would have been in the DEV folder - I can pet it when I get back home after the holidays... or you can get the include files (*.h) straight from the python source package and put them in /usr/include.

ever get back from that holiday of yours lol
still no dev files, I was helping a forum member with adding python to gimp so the "Script-fu" Xtns would work and needed python and pythongtk, so I sent him a link to your package and it worked with the additional package below on 2.14X
So then I went to compile a python app and guess what no dev files, lol

hmmm also noticed you misspelled your package name, should never have spaces in packages names you get a % in the name when you do. http://puppy-development.googlecode.com/files/Python%2B-2.6.4-i486.pet
ttuuxxx