build(pip): (deps): bump coverage from 6.0.2 to 6.2

[dependabot]

Bumps coverage from 6.0.2 to 6.2.

Changelog

Sourced from coverage's changelog.

Version 6.2 — 2021-11-26

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

.. _issue 989: nedbat/coveragepy#989 .. _issue 1012: nedbat/coveragepy#1012 .. _issue 1082: nedbat/coveragepy#1082 .. _issue 1203: nedbat/coveragepy#1203

.. _changes_612:

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 <issue 1270_>_.

• Fix: When remapping file paths through the [paths] setting while combining, the [run] relative_files setting was ignored, resulting in

... (truncated)

Commits

• 7a01882 docs: prep for 6.2
• 7c128a6 docs: sample html report
• fbd3c71 docs: tweak the description of --concurrency
• fb7b0e5 docs: tweak the latest changelog entry
• 9162ad0 test(refactor): avoid full commands to speed tests
• 8ca306e test(perf): shave a few seconds off the FailUnder tests
• c9d821d feat: multiple --concurrency values. #1012 #1082
• 97fdd55 build(docs): a target for running cog on the docs
• eff683c test(fix): keep SourceIncludeOmitTest's from clobbering each other
• 0865590 test(build): i've had the wrong -r character this whole time
• 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)

[github-actions]

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request}