Upgrading/unbundling coverage?

[Benoit Boissinot]

On Fri, Feb 26, 2010 at 9:30 AM, Dirkjan Ochtman <dirkjan at ochtman.nl> wrote:
> Hi there,
>
> 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.
>
> Anyone else has thoughts on this?

+1, it's for devs anyway, not users. So it should be fine.

Cheers,

Benoit