3.4, the latest release of my code coverage tool for Python, is now available. If you haven't been trying the betas, then new in this release are better ways to direct's's attention on your source code, a number of fixes to reporting, especially the XML report, and now completely unexecuted files can be reported as 0% covered.


tagged: , » 2 reactions


pankaj 4:57 AM on 25 Oct 2010

Hi Ned,
You may remember me requesting to add cython coverage. After some effort i've been able to make report cython functions coverage. Its a small patch, located at , with some test files at . If you feel its reasonable, i'd be glad if some such feature goes into
Currently it reports only function coverage (no line coverage), using profiling hooks.

pankaj 7:42 AM on 25 Oct 2010

i've fixed canonical_filename replacement for pyx files in case of absolute path in v2 of the file on the google site. waiting for ur comments on its feasibility :)

Add a comment:

Ignore this:
not displayed and no spam.
Leave this empty:
not searched.
Name and either email or www are required.
Don't put anything here:
Leave this empty:
URLs auto-link and some tags are allowed: <a><b><i><p><br><pre>.