Support multiple Pythons in the same working tree

This way you can run the tests against several python versions by doing

  make PYTHON_VER=2.6 build test
  make PYTHON_VER=2.7 build test
  make PYTHON_VER=3.2 build test

repeatedly, without having to re-download and recompile the respective
clean Python interpreters.
Ignore python$(PYTHON_VER) directories
Merge pull request #12 from mgedmin/multi-python

Support multiple Pythons in the same working tree
master is many things, but likely not version 1.4.x
travis: Test against Python 3.3rc1
document the Makefile for developer use
Clarify Makefile instructions, remove me from explicit travis sender list
removed failed attempt at isolation via -S
Merge pull request #16 from buildout/de-isolate

removed failed attempt at isolation via -S
sort unused options for consistent output.
Make exception expectation even vaguer. Sigh.

Sort dict-based data for consistent output.
Sort dict-based data for consistent output.
fix lazy server implementation cuz client is less forgiving in 3.3
Order of data in entry_points.txt is non-deterministic, especially in
Python 3.3, so we have to normalize data when computing package
hashes.
Evaluate options in sorted order to avoid spurious test failures.
Python3.3 generates a new meta-warning (about an unrecognized warning
option, -Wno-unused-result, which appears no where in buildout or
distribute code.  Ignore it.
My previous ellipsification added a newline where it shouldn't have.
Python 2.4 and 2.5 compat
Python 2.4 and 2.5 compat
Merge pull request #19 from buildout/3.3

3.3