6.3.3

• Fix: Coverage.py now builds successfully on CPython 3.11 (3.11.0b1) again. Closes issue 1367. Some results for generators may have changed.

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

6.3.2

• Fix: adapt to pypy3.9's decorator tracing behavior. It now traces function decorators like CPython 3.8: both the @-line and the def-line are traced. Fixes issue 1326.
• Debug: added pybehave to the list of coverage debug <cmd_debug> and cmd_run_debug options.
• Fix: show an intelligible error message if --concurrency=multiprocessing is used without a configuration file. Closes issue 1320.

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

6.3.1

• Fix: deadlocks could occur when terminating processes. Some of these deadlocks (described in issue 1310) are now fixed.
• Fix: a signal handler was being set from multiple threads, causing an error: "ValueError: signal only works in main thread". This is now fixed, closing issue 1312.
• Fix: --precision on the command-line was being ignored while considering --fail-under. This is now fixed, thanks to Marcelo Trylesinski.
• Fix: releases no longer provide 3.11.0-alpha wheels. Coverage.py uses CPython internal fields which are moving during the alpha phase. Fixes issue 1316.

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

6.3

• Feature: Added the lcov command to generate reports in LCOV format. Thanks, Bradley Burns. Closes issues 587 and 626.
• Feature: the coverage data file can now be specified on the command line with the --data-file option in any command that reads or writes data. This is in addition to the existing COVERAGE_FILE environment variable. Closes issue 624. Thanks, Nikita Bloshchanevich.
• Feature: coverage measurement data will now be written when a SIGTERM signal is received by the process. This includes Process.terminate <python:multiprocessing.Process.terminate>, and other ways to terminate a process. Currently this is only on Linux and Mac; Windows is not supported. Fixes issue 1307.
• Dropped support for Python 3.6, which reached end-of-life on 2021-12-23.
• Updated Python 3.11 support to 3.11.0a4, fixing issue 1294.
• Fix: the coverage data file is now created in a more robust way, to avoid problems when multiple processes are trying to write data at once. Fixes issues 1303 and 883.
• Fix: a .gitignore file will only be written into the HTML report output directory if the directory is empty. This should prevent certain unfortunate accidents of writing the file where it is not wanted.
• Releases now have MacOS arm64 wheels for Apple Silicon, fixing issue 1288.

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

6.2

• Feature: Now the --concurrency setting can have a list of values, so that threads and another lightweight threading package can be measured together, such as --concurrency=gevent,thread. Closes issue 1012 and issue 1082. This also means that thread must be explicitly specified in some cases that used to be implicit such as --concurrency=multiprocessing, which must be changed to --concurrency=multiprocessing,thread.
• Fix: A module specified as the source setting is imported during startup, before the user program imports it. This could cause problems if the rest of the program isn't ready yet. For example, issue 1203 describes a Django setting that is accessed before settings have been configured. Now the early import is wrapped in a try/except so errors then don't stop execution.
• Fix: A colon in a decorator expression would cause an exclusion to end too early, preventing the exclusion of the decorated function. This is now fixed.
• Fix: The HTML report now will not overwrite a .gitignore file that already exists in the HTML output directory (follow-on for issue 1244).
• API: The exceptions raised by Coverage.py have been specialized, to provide finer-grained catching of exceptions by third-party code.
• API: Using suffix=False when constructing a Coverage object with multiprocessing wouldn't suppress the data file suffix (issue 989). This is now fixed.
• Debug: The coverage debug data command will now sniff out combinable data files, and report on all of them.
• Debug: The coverage debug command used to accept a number of topics at a time, and show all of them, though this was never documented. This no longer works, to allow for command-line options in the future.

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

6.1.2

• Python 3.11 is supported (tested with 3.11.0a2). One still-open issue has to do with exits through with-statements.
• Fix: When remapping file paths through the [paths] setting while combining, the [run] relative_files setting was ignored, resulting in absolute paths for remapped file names (issue 1147). This is now fixed.
• Fix: Complex conditionals over excluded lines could have incorrectly reported a missing branch (issue 1271). This is now fixed.
• Fix: More exceptions are now handled when trying to parse source files for reporting. Problems that used to terminate coverage.py can now be handled with [report] ignore_errors. This helps with plugins failing to read files (django_coverage_plugin issue 78).
• Fix: Removed another vestige of jQuery from the source tarball (issue 840).
• Fix: Added a default value for a new-to-6.x argument of an internal class. This unsupported class is being used by coveralls (issue 1273). Although I'd rather not "fix" unsupported interfaces, it's actually nicer with a default value.

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

6.1.1

• Fix: The sticky header on the HTML report didn't work unless you had branch coverage enabled. This is now fixed: the sticky header works for everyone. (Do people still use coverage without branch measurement!? j/k)
• Fix: When using explicitly declared namespace packages, the "already imported a file that will be measured" warning would be issued (issue 888). This is now fixed.

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

6.1

• Deprecated: The annotate command and the Coverage.annotate function will be removed in a future version, unless people let me know that they are using it. Instead, the html command gives better-looking (and more accurate) output, and the report -m command will tell you line numbers of missing lines. Please get in touch if you have a reason to use annotate over those better options: ned@nedbatchelder.com.
• Feature: Coverage now sets an environment variable, COVERAGE_RUN when running your code with the coverage run command. The value is not important, and may change in the future. Closes issue 553.
• Feature: The HTML report pages for Python source files now have a sticky header so the file name and controls are always visible.
• Feature: The xml and json commands now describe what they wrote where.
• Feature: The html, combine, xml, and json commands all accept a -q/--quiet option to suppress the messages they write to stdout about what they are doing (issue 1254).
• Feature: The html command writes a .gitignore file into the HTML output directory, to prevent the report from being committed to git. If you want to commit it, you will need to delete that file. Closes issue 1244.
• Feature: Added support for PyPy 3.8.
• Fix: More generated code is now excluded from measurement. Code such as attrs boilerplate, or doctest code, was being measured though the synthetic line numbers meant they were never reported. Once Cython was involved though, the generated .so files were parsed as Python, raising syntax errors, as reported in issue 1160. This is now fixed.
• Fix: When sorting human-readable names, numeric components are sorted correctly: file10.py will appear after file9.py. This applies to file names, module names, environment variables, and test contexts.
• Performance: Branch coverage measurement is faster, though you might only notice on code that is executed many times, such as long-running loops.
• Build: jQuery is no longer used or vendored (issue 840 and issue 1118). Huge thanks to Nils Kattenbeck (septatrix) for the conversion to vanilla JavaScript in pull request 1248.

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

6.0.2

• Namespace packages being measured weren't properly handled by the new code that ignores third-party packages. If the namespace package was installed, it was ignored as a third-party package. That problem (issue 1231) is now fixed.
• Packages named as "source packages" (with source, or source_pkgs, or pytest-cov's --cov) might have been only partially measured. Their top-level statements could be marked as un-executed, because they were imported by coverage.py before measurement began (issue 1232). This is now fixed, but the package will be imported twice, once by coverage.py, then again by your test suite. This could cause problems if importing the package has side effects.
• The .CoverageData.contexts_by_lineno method was documented to return a dict, but was returning a defaultdict. Now it returns a plain dict. It also no longer returns negative numbered keys.

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

6.0.1

• In 6.0, the coverage.py exceptions moved from coverage.misc to coverage.exceptions. These exceptions are not part of the public supported API, CoverageException is. But a number of other third-party packages were importing the exceptions from coverage.misc, so they are now available from there again (issue 1226).
• Changed an internal detail of how tomli is imported, so that tomli can use coverage.py for their own test suite (issue 1228).
• Defend against an obscure possibility under code obfuscation, where a function can have an argument called "self", but no local named "self" (pull request 1210). Thanks, Ben Carlsson.

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