I tried actually doing a build on my home desktop, and none of these
run with python 3.3, which is /usr/bin/python on my home desktop.

There may be a way to use third_party's protobuf (and this
may eventually be necessary) but I haven't yet figured out
how to do it correctly. It can happen later.

The source code is moved from src/python to
src/python/src. A setup.py is added at
src/python. The build_python.sh and
run_python.sh scripts are updated to build
and run the Python tests by building a
package and installing it in the developer's
Python 2.7 virtual environment.

Refactor the code a little to make this easier to munge around.

Run faster on smaller machines.

Don't watch '.' prefixed files for changes. These files don't typically contribute to builds, and are used as vim temp files.

Add a template to generate a complete list of tests for C/C++, and use it to generate the list of binaries to run tests for.

Instead of third party simplejson module, to save a dependency.

By default don't re-run tests that have already run successfully, to
reduce latency between making a change and seeing if it fixed the last
thing that you were trying to fix.