Update coverage requirement from <5.0 to <6.0

[dependabot-preview]

Updates the requirements on coverage to permit the latest version.

Changelog

Sourced from coverage's changelog.

Version 5.0.1 --- 2019-12-22

• If a 4.x data file is the cause of a "file is not a database" error, then use a more specific error message, "Looks like a coverage 4.x data file, are you mixing versions of coverage?" Helps diagnose the problems described in issue 886.
• Measurement contexts and relative file names didn't work together, as reported in issue 899 and issue 900. This is now fixed, thanks to David Szotten.
• When using coverage run --concurrency=multiprocessing, all data files should be named with parallel-ready suffixes. 5.0 mistakenly named the main process' file with no suffix when using --append. This is now fixed, closing issue 880.
• Fixed a problem on Windows when the current directory is changed to a different drive (issue 895). Thanks, Olivier Grisel.
• Updated Python 3.9 support to 3.9a2.

Version 5.0 --- 2019-12-14

Nothing new beyond 5.0b2.

Version 5.0b2 --- 2019-12-08

• An experimental [run] relative_files setting tells coverage to store relative file names in the data file. This makes it easier to run tests in one (or many) environments, and then report in another. It has not had much real-world testing, so it may change in incompatible ways in the future.
• When constructing a coverage.Coverage object, data_file can be specified as None to prevent writing any data file at all. In previous versions, an explicit data_file=None argument would use the default of ".coverage". Fixes issue 871.
• Python files run with -m now have __spec__ defined properly. This fixes issue 745 (about not being able to run unittest tests that spawn subprocesses), and issue 838, which described the problem directly.
• The [paths] configuration section is now ordered. If you specify more than one list of patterns, the first one that matches will be used. Fixes issue 649.
• The .coverage.numbits.register_sqlite_functions function now also registers numbits_to_nums for use in SQLite queries. Thanks, Simon Willison.
• Python 3.9a1 is supported.
• Coverage.py has a mascot: Sleepy Snake <sleepy>.

Version 5.0b1 --- 2019-11-11

• The HTML and textual reports now have a --skip-empty option that skips files with no statements, notably __init__.py files. Thanks, Reya B.
• Configuration can now be read from TOML files. This requires installing coverage.py with the [toml] extra. The standard "pyproject.toml" file will be read automatically if no other configuration file is found, with settings in the [tool.coverage.] namespace. Thanks to Frazer McLean for implementation and persistence. Finishes issue 664.
• The [run] note setting has been deprecated. Using it will result in a warning, and the note will not be written to the data file. The corresponding .CoverageData methods have been removed.
• The HTML report has been reimplemented (no more table around the source code). This allowed for a better presentation of the context information, hopefully resolving issue 855.
• Added sqlite3 module version information to coverage debug sys output.
• Asking the HTML report to show contexts ([html] show_contexts=True or coverage html --show-contexts) will issue a warning if there were no contexts measured (issue 851).

Version 5.0a8 --- 2019-10-02

• The .CoverageData API has changed how queries are limited to specific contexts. Now you use .CoverageData.set_query_context to set a single exact-match string, or .CoverageData.set_query_contexts to set a list of regular expressions to match contexts. This changes the command-line --contexts option to use regular expressions instead of filename-style wildcards.

Version 5.0a7 --- 2019-09-21

• Data can now be "reported" in JSON format, for programmatic use, as requested in issue 720. The new coverage json command writes raw and summarized data to a JSON file. Thanks, Matt Bachmann.
• Dynamic contexts are now supported in the Python tracer, which is important for PyPy users. Closes issue 846.
• The compact line number representation introduced in 5.0a6 is called a "numbits." The coverage.numbits module provides functions for working with them.
• The reporting methods used to permanently apply their arguments to the configuration of the Coverage object. Now they no longer do. The arguments affect the operation of the method, but do not persist.
• A class named "test_something" no longer confuses the test_function dynamic context setting. Fixes issue 829.
• Fixed an unusual tokenizing issue with backslashes in comments. Fixes issue 822.
• debug=plugin didn't properly support configuration or dynamic context plugins, but now it does, closing issue 834.

... (truncated)

Commits

• d2ae0e2 Prep for 5.0.1
• 7e747a3 Re-order windows CI jobs to get more useful information earlier
• 0d6a878 Detect when a 4.x data file is being read. #886
• d66d496 Don't need to check for JSON-era bad-data messages any more
• 77dc37f Tweak some coverage details of switch_context code
• cecc5dd One more adjustment for Python 3.9a2
• 28c29a7 bpo 39114 broke 3.9, but maybe it's their bug
• 31f7280 Cleanup and changelog for #899 #900
• ade1f2c fix context reporting for relative_files
• 7dc3772 Python 3.9a2 reverted how argv[0] is handled
• 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[NotAFile]

Yeah this was held back because of it breaking coveralls

[NotAFile]

TheKevJames/coveralls-python#203 (comment)

we should rerun this to see if it works now

[NotAFile]

@dependabot rebase

[dependabot-preview]

Looks like this PR is already up-to-date with master! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[NotAFile]

@dependabot recreate