[RFC] depend on testtools for testing?

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...

> 
> On the other hand, even for subunit which has a moderately sane
> maintainer, getting a feature in did take noticeably longer than it
> might have in bzr.
> 
> I agree with John's summary of some of the specific problems, and am
> also ambivalent about taking such a change, defaulting to no.
> 
> Things that would move me away from that default:
> 
>  1- folks like Alexander who will be bitten about this saying "it's
> really not a problem and a great idea" (or the opposite)
> 
>  2- the new dependency having actual compelling feature improvements
> beyond what's in Bazaar
> 

Well, I feel like one of Robert's pushes is that he doesn't want to make
bzr's testing infrastructure compatible with the "standard way" of doing
things, so that we can actually use --subunit on pqm. In that light, I
can agree that it would be nicer to build on a tool that can be tweaked
to conform to the standard, rather than having to do that work in 2 places.

I *did* like seeing a progress bar on PQM. I also liked getting a reject
email that had all of the content and could be filtered more easily than
just scrolling.

I found subunit itself rather hard to install, because it is all based
on an autoconf setup, because it adds support for more-than-just python.
On Windows, that is just a lot of pain for me to try to work out. A
'setup.py' that *only* built/installed the python portion would have
helped a lot there, and 'testtools' would be pure-python, so should
avoid it. (I did an end-run and just run from source, but that isn't
trivial either because of where the lib dir is versus the binaries,
versus where 'python' is on my path, etc.)

I don't really know that getting a progress bar on PQM is worth the
negatives of adding a dependency on a moving 'testtools' target...

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrqCHEACgkQJdeBCYSNAAPB2gCdF8HuwHWSkbFrQjLtV15fqFya
oRUAn2DnPtdyQS/6HNxG+HktDzfGIxHN
=bjmA
-----END PGP SIGNATURE-----