3.5.3

Version 3.5.3 — 2012-09-29

• Line numbers in the HTML report line up better with the source lines, fixing issue 197, thanks Marius Gedminas.
• When specifying a directory as the source= option, the directory itself no longer needs to have a __init__.py file, though its sub-directories do, to be considered as source files.
• Files encoded as UTF-8 with a BOM are now properly handled, fixing issue 179. Thanks, Pablo Carballo.
• Fixed more cases of non-Python files being reported as Python source, and then not being able to parse them as Python. Closes issue 82 (again). Thanks, Julian Berman.
• Fixed memory leaks under Python 3, thanks, Brett Cannon. Closes issue 147.
• Optimized .pyo files may not have been handled correctly, issue 195. Thanks, Marius Gedminas.
• Certain unusually named file paths could have been mangled during reporting, issue 194. Thanks, Marius Gedminas.
• Try to do a better job of the impossible task of detecting when we can’t build the C extension, fixing issue 183.
• Testing is now done with tox, thanks, Marc Abramowitz.

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

3.5.2

Version 3.5.2 — 2012-05-04

No changes since 3.5.2.b1

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

3.5.2b1

Version 3.5.2b1 — 2012-04-29

• The HTML report has slightly tweaked controls: the buttons at the top of the page are color-coded to the source lines they affect.
• Custom CSS can be applied to the HTML report by specifying a CSS file as the extra_css configuration value in the [html] section.
• Source files with custom encodings declared in a comment at the top are now properly handled during reporting on Python 2. Python 3 always handled them properly. This fixes issue 157.
• Backup files left behind by editors are no longer collected by the source= option, fixing issue 168.
• If a file doesn’t parse properly as Python, we don’t report it as an error if the file name seems like maybe it wasn’t meant to be Python. This is a pragmatic fix for issue 82.
• The -m switch on coverage report, which includes missing line numbers in the summary report, can now be specified as show_missing in the config file. Closes issue 173.
• When running a module with coverage run -m <modulename>, certain details of the execution environment weren’t the same as for python -m <modulename>. This had the unfortunate side-effect of making coverage run -m unittest discover not work if you had tests in a directory named “test”. This fixes issue 155 and issue 142.
• Now the exit status of your product code is properly used as the process status when running python -m coverage run .... Thanks, JT Olds.
• When installing into PyPy, we no longer attempt (and fail) to compile the C tracer function, closing issue 166.

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

3.5.1

Version 3.5.1 — 2011-09-23

• The [paths] feature unfortunately didn’t work in real world situations where you wanted to, you know, report on the combined data. Now all paths stored in the combined file are canonicalized properly.

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

3.5.1b1

Version 3.5.1b1 — 2011-08-28

• When combining data files from parallel runs, you can now instruct coverage.py about which directories are equivalent on different machines. A [paths] section in the configuration file lists paths that are to be considered equivalent. Finishes issue 17.
• for-else constructs are understood better, and don’t cause erroneous partial branch warnings. Fixes issue 122.
• Branch coverage for with statements is improved, fixing issue 128.
• The number of partial branches reported on the HTML summary page was different than the number reported on the individual file pages. This is now fixed.
• An explicit include directive to measure files in the Python installation wouldn’t work because of the standard library exclusion. Now the include directive takes precedence, and the files will be measured. Fixes issue 138.
• The HTML report now handles Unicode characters in Python source files properly. This fixes issue 124 and issue 144. Thanks, Devin Jeanpierre.
• In order to help the core developers measure the test coverage of the standard library, Brandon Rhodes devised an aggressive hack to trick Python into running some coverage.py code before anything else in the process. See the coverage/fullcoverage directory if you are interested.

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

3.5

Version 3.5 — 2011-06-29

• The HTML report hotkeys now behave slightly differently when the current chunk isn’t visible at all: a chunk on the screen will be selected, instead of the old behavior of jumping to the literal next chunk. The hotkeys now work in Google Chrome. Thanks, Guido van Rossum.

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

3.5b1

Version 3.5b1 — 2011-06-05

• The HTML report now has hotkeys. Try n, s, m, x, b, p, and c on the overview page to change the column sorting. On a file page, r, m, x, and p toggle the run, missing, excluded, and partial line markings. You can navigate the highlighted sections of code by using the j and k keys for next and previous. The 1 (one) key jumps to the first highlighted section in the file, and 0 (zero) scrolls to the top of the file.
• The --omit and --include switches now interpret their values more usefully. If the value starts with a wildcard character, it is used as-is. If it does not, it is interpreted relative to the current directory. Closes issue 121.
• Partial branch warnings can now be pragma’d away. The configuration option partial_branches is a list of regular expressions. Lines matching any of those expressions will never be marked as a partial branch. In addition, there’s a built-in list of regular expressions marking statements which should never be marked as partial. This list includes while True:, while 1:, if 1:, and if 0:.
• The coverage() constructor accepts single strings for the omit= and include= arguments, adapting to a common error in programmatic use.
• Modules can now be run directly using coverage run -m modulename, to mirror Python’s -m flag. Closes issue 95, thanks, Brandon Rhodes.
• coverage run didn’t emulate Python accurately in one small detail: the current directory inserted into sys.path was relative rather than absolute. This is now fixed.
• HTML reporting is now incremental: a record is kept of the data that produced the HTML reports, and only files whose data has changed will be generated. This should make most HTML reporting faster.
• Pathological code execution could disable the trace function behind our backs, leading to incorrect code measurement. Now if this happens, coverage.py will issue a warning, at least alerting you to the problem. Closes issue 93. Thanks to Marius Gedminas for the idea.
• The C-based trace function now behaves properly when saved and restored with sys.gettrace() and sys.settrace(). This fixes issue 125 and issue 123. Thanks, Devin Jeanpierre.
• Source files are now opened with Python 3.2’s tokenize.open() where possible, to get the best handling of Python source files with encodings. Closes issue 107, thanks, Brett Cannon.
• Syntax errors in supposed Python files can now be ignored during reporting with the -i switch just like other source errors. Closes issue 115.
• Installation from source now succeeds on machines without a C compiler, closing issue 80.
• Coverage.py can now be run directly from a working tree by specifying the directory name to python: python coverage_py_working_dir run .... Thanks, Brett Cannon.
• A little bit of Jython support: coverage run can now measure Jython execution by adapting when $py.class files are traced. Thanks, Adi Roiban. Jython still doesn’t provide the Python libraries needed to make coverage reporting work, unfortunately.
• Internally, files are now closed explicitly, fixing issue 104. Thanks, Brett Cannon.

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

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