coverage module is one of the most sturdy and reliable pillars of my development toolset. It’s a hallmark of a great tool that you never have to spend too much with it— When I want to check the statement-coverage of my tests, I just use
coverage (invoked via its Nose plugin), it just works, and then I can go back to writing my tests and ensuring they cover a big part of my code. You don’t have to spend too much time with it for the simple reason that it very rarely breaks— Which is not a trivial accomplishment for a tool that acts on every, single, line of code in your project.
Kudos to Ned Batchelder for his excellent maintenance of the
coverage module! I’m a relatively new user of
coverage, having used it only for about 2 years, if I remember correctly. So long-time users of
coverage may have a bigger perspective on this module than I do. But in the relatively short time that I’ve been using it, Ned has been an exemplary maintainer, and the few tickets that I created on the bug tracker received his attention. Ned also made sure that
coverage supported Python 3.x before it was cool, and on every release he takes the time to create Windows binaries of
coverage to help Windows users avoid having to compile it themselves.
If every maintainer was as dedicated as Ned, the Python community would be in a better place today, and we would have probably already seen Python 3.x going into mainstream.
Thank you, Gareth and Ned, for this wonderful module!