6.4.2

Version 6.4.2 — 2022-07-12

• Updated for a small change in Python 3.11.0 beta 4: modules now start with a line with line number 0, which is ignored. This line cannot be executed, so coverage totals were thrown off. This line is now ignored by coverage.py, but this also means that truly empty modules (like __init__.py) have no lines in them, rather than one phantom line. Fixes issue 1419.
• Internal debugging data added to sys.modules is now an actual module, to avoid confusing code that examines everything in sys.modules. Thanks, Yilei Yang.

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

6.4.1

Version 6.4.1 — 2022-06-02

• Greatly improved performance on PyPy, and other environments that need the pure Python trace function. Thanks, Carl Friedrich Bolz-Tereick (pull 1381 and pull 1388). Slightly improved performance when using the C trace function, as most environments do. Closes issue 1339.
• The conditions for using tomllib from the standard library have been made more precise, so that 3.11 alphas will continue to work. Closes issue 1390.

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

6.4

Version 6.4 — 2022-05-22

• A new setting, [run] sigterm, controls whether a SIGTERM signal handler is used. In 6.3, the signal handler was always installed, to capture data at unusual process ends. Unfortunately, this introduced other problems (see issue 1310). Now the signal handler is only used if you opt-in by setting [run] sigterm = true.
• Small changes to the HTML report:
  • Added links to next and previous file, and more keyboard shortcuts: [ and ] for next file and previous file; u for up to the index; and ? to open/close the help panel. Thanks, J. M. F. Tsang.
  • The time stamp and version are displayed at the top of the report. Thanks, Ammar Askar. Closes issue 1351.
• A new debug option debug=sqldata adds more detail to debug=sql, logging all the data being written to the database.
• Previously, running coverage report (or any of the reporting commands) in an empty directory would create a .coverage data file. Now they do not, fixing issue 1328.
• On Python 3.11, the [toml] extra no longer installs tomli, instead using tomllib from the standard library. Thanks Shantanu.
• In-memory CoverageData objects now properly update(), closing issue 1323.

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

6.3.3

Version 6.3.3 — 2022-05-12

• 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

Version 6.3.2 — 2022-02-20

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

Version 6.3.1 — 2022-02-01

• 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

Version 6.3 — 2022-01-25

• 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 https://docs.python.org/3/library/multiprocessing.html#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

Version 6.2 — 2021-11-26

• 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

Version 6.1.2 — 2021-11-10

• 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

Version 6.1.1 — 2021-10-31

• 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