Upgrading/unbundling coverage?

[Thomas Arendsen Hein]

* Dirkjan Ochtman <dirkjan at ochtman.nl> [20100226 10:27]:
> At PyCon, I sprinted with the coverage.py developer on fixing it up so
> that it can trace through subprocesses. This means that we should be
> able to get accurate coverage results for things like hgweb. To enable
> this, we need to upgrade to coverage.py 3.3. However, in this version
> coverage.py has become a package. Also, I find that keeping external
> code in our tree can be a bit of a pain (for example with check-code),
> so I wonder if maybe we should unbundle coverage from our tree and
> simply have the --cover option (and related options) error out if
> coverage isn't available.

You just pushed this change to the stable branch instead of to
default, was this intentional or a mistake?
I can't say that this completely wrong, because this only affects
developers, but is still a bit surprising.

Besides this, version 3.3 is not available in Debian (only 2.85 in
squeeze/sid), see http://bugs.debian.org/535764 (which mentions 3.2
as waiting for a sponsor) since February 2010).

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner