Depend on unittest2.

unittest2 has backports of discover etc which allows us to make it a
stock feature rather than something that is present sometimes, and
which we have to carry ugly monkey patches for.

Change-Id: Ib30a4a9de8c58edf5d9c4ea5e06d49b0c821f12f
Fixup travis. OOPS.

Change-Id: Ia03284a3ca79c66e0f1e56a526c6b18a70aca687
Improve support for discovery on testtools.tests.

Our tests currently import test_with_with into test_testcase so that
we could still run tests on python2.5. Since we no longer support
2.5, we don't need this hack. Its a hack because discovery will
import test_with_with directly itself, and thus we triggered
a duplicate test id error when attempting to use discover on the
testtools test base.

Change-Id: I027929ab4b0df350dd18ab01ffd5c493fe35e101
Make discover run the same tests as 'make test'.

We use test parameterisation in test_deferredruntest, but hadn't
defined a load_tests hook to inform discover of that.

Change-Id: Ib32d7cf88b1a9e311476a5286357e46e65de1f1f
Update testtools.compat.__all__.

Remove references to functions that have been removed in
deedadf3750c16c2f26c5680a158ac96ca10ccd6 from __all__.
Merge pull request #117 from jelmer/all-all

Update testtools.compat.__all__.
Use unittest2 TestProgram implementation.

This brings in many fixes made to discovery where previously we were only using
the discovery package or the version in the release of Python that the test
execution was occuring on. (Robert Collins, #1271133)

Change-Id: I6270c8e8949262c01cb3a4e40735077ad6fc1ef2
Pin Pygments below 2.0 for our 3.2 build.

See https://bitbucket.org/birkenfeld/pygments-main/issue/1054

Change-Id: I79baae6f4fcf9b453b25c2e1587474d94da73b79
Expand test matrix to include Python 3.4 and pypy3

Change-Id: I607530d8fc1846acbe7d0150fddac166e79a0910