coverage-3.2b2

• Branch coverage improvements:
  • Classes are no longer incorrectly marked as branches: issue 32.
  • “except” clauses with types are no longer incorrectly marked as branches: issue 35.
• Fixed some problems syntax coloring sources with line continuations and source with tabs: issue 30 and issue 31.
• The –omit option now works much better than before, fixing issue 14 and issue 33. Thanks, Danek Duvall.

coverage-3.2b1

• Branch coverage!
• XML reporting has file paths that let Cobertura find the source code.
• The tracer code has changed, it’s a few percent faster.
• Some exceptions reported by the command line interface have been cleaned up so that tracebacks inside coverage.py aren’t shown. Fixes issue 23.

coverage-3.1

• Source code can now be read from eggs. Thanks, Ross Lawley. Fixes issue 25.

coverage-3.1b1

• Python 3.1 is now supported.
• Coverage.py has a new command line syntax with sub-commands. This expands the possibilities for adding features and options in the future. The old syntax is still supported. Try “coverage help” to see the new commands. Thanks to Ben Finney for early help.
• Added an experimental “coverage xml” command for producing coverage reports in a Cobertura-compatible XML format. Thanks, Bill Hart.
• Added the –timid option to enable a simpler slower trace function that works for DecoratorTools projects, including TurboGears. Fixed issue 12 and issue 13.
• HTML reports show modules from other directories. Fixed issue 11.
• HTML reports now display syntax-colored Python source.
• Programs that change directory will still write .coverage files in the directory where execution started. Fixed issue 24.
• Added a “coverage debug” command for getting diagnostic information about the coverage.py installation.

coverage-3.0.1

• Removed the recursion limit in the tracer function. Previously, code that ran more than 500 frames deep would crash. Fixed issue 9.
• Fixed a bizarre problem involving pyexpat, whereby lines following XML parser invocations could be overlooked. Fixed issue 10.
• On Python 2.3, coverage.py could mis-measure code with exceptions being raised. This is now fixed.
• The coverage.py code itself will now not be measured by coverage.py, and no coverage.py modules will be mentioned in the nose –with-cover plug-in. Fixed issue 8.
• When running source files, coverage.py now opens them in universal newline mode just like Python does. This lets it run Windows files on Mac, for example.

coverage-3.0

• Fixed the way the Python library was ignored. Too much code was being excluded the old way.
• Tabs are now properly converted in HTML reports. Previously indentation was lost. Fixed issue 6.
• Nested modules now get a proper flat_rootname. Thanks, Christian Heimes.

coverage-3.0b3

• Added parameters to coverage.__init__ for options that had been set on the coverage object itself.
• Added clear_exclude() and get_exclude_list() methods for programmatic manipulation of the exclude regexes.
• Added coverage.load() to read previously-saved data from the data file.
• Improved the finding of code files. For example, .pyc files that have been installed after compiling are now located correctly. Thanks, Detlev Offenbach.
• When using the object API (that is, constructing a coverage() object), data is no longer saved automatically on process exit. You can re-enable it with the auto_data=True parameter on the coverage() constructor. The module-level interface still uses automatic saving.

coverage-3.0b1

Major overhaul.

• Coverage.py is now a package rather than a module. Functionality has been split into classes.
• The trace function is implemented in C for speed. Coverage.py runs are now much faster. Thanks to David Christian for productive micro-sprints and other encouragement.
• Executable lines are identified by reading the line number tables in the compiled code, removing a great deal of complicated analysis code.
• Precisely which lines are considered executable has changed in some cases. Therefore, your coverage stats may also change slightly.
• The singleton coverage object is only created if the module-level functions are used. This maintains the old interface while allowing better programmatic use of coverage.py.
• The minimum supported Python version is 2.3.