3.4

Version 3.4 — 2010-09-19

• The XML report is now sorted by package name, fixing issue 88.
• Programs that exited with sys.exit() with no argument weren’t handled properly, producing a coverage.py stack trace. That is now fixed.

➡️  PyPI page: coverage 3.4.
➡️  To install: python3 -m pip install coverage==3.4

3.4b2

Version 3.4b2 — 2010-09-06

• Completely un-executed files can now be included in coverage results, reported as 0% covered. This only happens if the –source option is specified, since coverage.py needs guidance about where to look for source files.
• The XML report output now properly includes a percentage for branch coverage, fixing issue 65 and issue 81.
• Coverage percentages are now displayed uniformly across reporting methods. Previously, different reports could round percentages differently. Also, percentages are only reported as 0% or 100% if they are truly 0 or 100, and are rounded otherwise. Fixes issue 41 and issue 70.
• The precision of reported coverage percentages can be set with the [report] precision config file setting. Completes issue 16.
• Threads derived from threading.Thread with an overridden run method would report no coverage for the run method. This is now fixed, closing issue 85.

➡️  PyPI page: coverage 3.4b2.
➡️  To install: python3 -m pip install coverage==3.4b2

3.4b1

Version 3.4b1 — 2010-08-21

• BACKWARD INCOMPATIBILITY: the --omit and --include switches now take file patterns rather than file prefixes, closing issue 34 and issue 36.
• BACKWARD INCOMPATIBILITY: the omit_prefixes argument is gone throughout coverage.py, replaced with omit, a list of file name patterns suitable for fnmatch. A parallel argument include controls what files are included.
• The run command now has a --source switch, a list of directories or module names. If provided, coverage.py will only measure execution in those source files.
• Various warnings are printed to stderr for problems encountered during data measurement: if a --source module has no Python source to measure, or is never encountered at all, or if no data is collected.
• The reporting commands (report, annotate, html, and xml) now have an --include switch to restrict reporting to modules matching those file patterns, similar to the existing --omit switch. Thanks, Zooko.
• The run command now supports --include and --omit to control what modules it measures. This can speed execution and reduce the amount of data during reporting. Thanks Zooko.
• Since coverage.py 3.1, using the Python trace function has been slower than it needs to be. A cache of tracing decisions was broken, but has now been fixed.
• Python 2.7 and 3.2 have introduced new opcodes that are now supported.
• Python files with no statements, for example, empty __init__.py files, are now reported as having zero statements instead of one. Fixes issue 1.
• Reports now have a column of missed line counts rather than executed line counts, since developers should focus on reducing the missed lines to zero, rather than increasing the executed lines to varying targets. Once suggested, this seemed blindingly obvious.
• Line numbers in HTML source pages are clickable, linking directly to that line, which is highlighted on arrival. Added a link back to the index page at the bottom of each HTML page.
• Programs that call os.fork will properly collect data from both the child and parent processes. Use coverage run -p to get two data files that can be combined with coverage combine. Fixes issue 56.
• Coverage.py is now runnable as a module: python -m coverage. Thanks, Brett Cannon.
• When measuring code running in a virtualenv, most of the system library was being measured when it shouldn’t have been. This is now fixed.
• Doctest text files are no longer recorded in the coverage data, since they can’t be reported anyway. Fixes issue 52 and issue 61.
• Jinja HTML templates compile into Python code using the HTML file name, which confused coverage.py. Now these files are no longer traced, fixing issue 82.
• Source files can have more than one dot in them (foo.test.py), and will be treated properly while reporting. Fixes issue 46.
• Source files with DOS line endings are now properly tokenized for syntax coloring on non-DOS machines. Fixes issue 53.
• Unusual code structure that confused exits from methods with exits from classes is now properly analyzed. See issue 62.
• Asking for an HTML report with no files now shows a nice error message rather than a cryptic failure (‘int’ object is unsubscriptable). Fixes issue 59.

➡️  PyPI page: coverage 3.4b1.
➡️  To install: python3 -m pip install coverage==3.4b1

3.3.1

Version 3.3.1 — 2010-03-06

• Using parallel=True in .coveragerc file prevented reporting, but now does not, fixing issue 49.
• When running your code with “coverage run”, if you call sys.exit(), coverage.py will exit with that status code, fixing issue 50.

➡️  PyPI page: coverage 3.3.1.
➡️  To install: python3 -m pip install coverage==3.3.1

3.3

Version 3.3 — 2010-02-24

• Settings are now read from a .coveragerc file. A specific file can be specified on the command line with –rcfile=FILE. The name of the file can be programmatically set with the config_file argument to the coverage() constructor, or reading a config file can be disabled with config_file=False.
• Fixed a problem with nested loops having their branch possibilities mis-characterized: issue 39.
• Added coverage.process_start to enable coverage measurement when Python starts.
• Parallel data file names now have a random number appended to them in addition to the machine name and process id.
• Parallel data files combined with “coverage combine” are deleted after they’re combined, to clean up unneeded files. Fixes issue 40.
• Exceptions thrown from product code run with “coverage run” are now displayed without internal coverage.py frames, so the output is the same as when the code is run without coverage.py.
• The data_suffix argument to the coverage constructor is now appended with an added dot rather than simply appended, so that .coveragerc files will not be confused for data files.
• Python source files that don’t end with a newline can now be executed, fixing issue 47.
• Added an AUTHORS.txt file.

➡️  PyPI page: coverage 3.3.
➡️  To install: python3 -m pip install coverage==3.3

3.2

Version 3.2 — 2009-12-05

• Added a --version option on the command line.

➡️  PyPI page: coverage 3.2.
➡️  To install: python3 -m pip install coverage==3.2

3.2b4

Version 3.2b4 — 2009-12-01

• Branch coverage improvements:
  • The XML report now includes branch information.
• Click-to-sort HTML report columns are now persisted in a cookie. Viewing a report will sort it first the way you last had a coverage report sorted. Thanks, Chris Adams.
• On Python 3.x, setuptools has been replaced by Distribute.

➡️  PyPI page: coverage 3.2b4.
➡️  To install: python3 -m pip install coverage==3.2b4

3.2b3

Version 3.2b3 — 2009-11-23

• Fixed a memory leak in the C tracer that was introduced in 3.2b1.
• Branch coverage improvements:
  • Branches to excluded code are ignored.
• The table of contents in the HTML report is now sortable: click the headers on any column. Thanks, Chris Adams.

➡️  PyPI page: coverage 3.2b3.
➡️  To install: python3 -m pip install coverage==3.2b3

3.2b2

Version 3.2b2 — 2009-11-19

• 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.

➡️  PyPI page: coverage 3.2b2.
➡️  To install: python3 -m pip install coverage==3.2b2

3.2b1

Version 3.2b1 — 2009-11-10

• 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.

➡️  PyPI page: coverage 3.2b1.
➡️  To install: python3 -m pip install coverage==3.2b1