Bump coverage[toml] from 5.3 to 6.3.3

[dependabot]

Bumps coverage[toml] from 5.3 to 6.3.3.

Release notes

Sourced from coverage[toml]'s releases.

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.

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 Diagnostics: coverage debug and --debug options.
• Fix: show an intelligible error message if --concurrency=multiprocessing is used without a configuration file. Closes issue 1320.

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.

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

6.2

• Feature: Now the --concurrency setting can now 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.
• 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.

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.

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.

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: https://github.com/nedbat/coveragepy/blob/HEAD/mailto: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.

... (truncated)

Changelog

Sourced from coverage[toml]'s changelog.

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.

.. _issue 1367: nedbat/coveragepy#1367

.. _changes_632:

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 :ref:cmd_debug and :ref:cmd_run_debug options.

• Fix: show an intelligible error message if --concurrency=multiprocessing is used without a configuration file. Closes issue 1320_.

.. _issue 1320: nedbat/coveragepy#1320 .. _issue 1326: nedbat/coveragepy#1326

.. _changes_631:

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 <pull 1317_>_.

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

.. _issue 1310: nedbat/coveragepy#1310 .. _issue 1312: nedbat/coveragepy#1312 .. _issue 1316: nedbat/coveragepy#1316

... (truncated)

Commits

• 99ab688 docs: latest sample
• c01fc71 build: prep for 6.3.3
• ce2d4ec build: don't make wheels for pre-release Pythons
• a9ecd8a build: add markdown summary to the action
• 3e6ff4f chore: make upgrade
• e5b91eb test: skip tests that fail until CPython #92236 is fixed
• 956f0fd fix: fix compilation errors on latest 3.11.0
• 9097c0d debug: incidental debug improvements in tracer.c
• 45ba7e7 build(deps): bump docker/setup-qemu-action from 1 to 2 (#1372)
• 9ef7d3c build: Set permissions for GitHub actions (#1369)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #273.