There is one at the top level (right next to generate_site.bash), and one down inside springpython/src as well as springpython/samples.
The idea is to use the top-level build.py directly:
THAT script isn't a convention setup.py script, but instead a sort of top-level make file-like thing.
Clean out target directory and run test suite.
Clean out target directory and generate installable tar bundles (with classic setup.py scripts included inside the bundle).
./build.py --clean --test
After that last command, you should be able to go down to springpython/src, and run:
./build.py --clean --package
...and have the whole library install itself on your machine.
python setup.py install
Down inside springpython/src and springpython/samples, there is also a build.py script. It is a template (perhaps I should rename to show that more clearly). The top-level build.py will use that lower level build.py as input to generate a setup.py script with the version number of the release inserted into it.
It is best to think of top-level build.py as more analogous to build.xml for ant jobs. That is the thinking I needed to use in order to better integrate with SpringSource's build/deploy/package/release mechanism.