Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump coverage from 5.3.1 to 6.0.1 #44

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Oct 7, 2021

Bumps coverage from 5.3.1 to 6.0.1.

Release notes

Sourced from coverage's releases.

coverage-5.6b1

  • Third-party packages are now ignored in coverage reporting. This solves a few problems:
    • Coverage will no longer report about other people’s code (issue 876). This is true even when using --source=. with a venv in the current directory.
    • Coverage will no longer generate “Already imported a file that will be measured” warnings about coverage itself (issue 905).
  • The HTML report uses j/k to move up and down among the highlighted chunks of code. They used to highlight the current chunk, but 5.0 broke that behavior. Now the highlighting is working again.
  • The JSON report now includes percent_covered_display, a string with the total percentage, rounded to the same number of decimal places as the other reports’ totals.

coverage-5.5

  • coverage combine has a new option, --keep to keep the original data files after combining them. The default is still to delete the files after they have been combined. This was requested in issue 1108 and implemented in pull request 1110. Thanks, Éric Larivière.
  • When reporting missing branches in coverage report, branches aren’t reported that jump to missing lines. This adds to the long-standing behavior of not reporting branches from missing lines. Now branches are only reported if both the source and destination lines are executed. Closes both issue 1065 and issue 955.
  • Minor improvements to the HTML report:
    • The state of the line visibility selector buttons is saved in local storage so you don’t have to fiddle with them so often, fixing issue 1123.
    • It has a little more room for line numbers so that 4-digit numbers work well, fixing issue 1124.
  • Improved the error message when combining line and branch data, so that users will be more likely to understand what’s happening, closing issue 803.

coverage-5.4

  • The text report produced by coverage report now always outputs a TOTAL line, even if only one Python file is reported. This makes regex parsing of the output easier. Thanks, Judson Neer. This had been requested a number of times (issue 1086, issue 922, issue 732).
  • The skip_covered and skip_empty settings in the configuration file can now be specified in the [html] section, so that text reports and HTML reports can use separate settings. The HTML report will still use the [report] settings if there isn’t a value in the [html] section. Closes issue 1090.
  • Combining files on Windows across drives now works properly, fixing issue 577. Thanks, Valentin Lab.
  • Fix an obscure warning from deep in the _decimal module, as reported in issue 1084.
  • Update to support Python 3.10 alphas in progress, including PEP 626: Precise line numbers for debugging and other tools.
Changelog

Sourced from coverage's changelog.

Version 6.0.1 --- 2021-10-06

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

.. _pull request 1210: nedbat/coveragepy#1210 .. _issue 1226: nedbat/coveragepy#1226 .. _issue 1228: nedbat/coveragepy#1228

.. _changes_60:

Version 6.0 --- 2021-10-03

  • The coverage html command now prints a message indicating where the HTML report was written. Fixes issue 1195_.

  • The coverage combine command now prints messages indicating each data file being combined. Fixes issue 1105_.

  • The HTML report now includes a sentence about skipped files due to skip_covered or skip_empty settings. Fixes issue 1163_.

  • Unrecognized options in the configuration file are no longer errors. They are now warnings, to ease the use of coverage across versions. Fixes issue 1035_.

  • Fix handling of exceptions through context managers in Python 3.10. A missing exception is no longer considered a missing branch from the with statement. Fixes issue 1205_.

  • Fix another rarer instance of "Error binding parameter 0 - probably unsupported type." (issue 1010_).

  • Creating a directory for the coverage data file now is safer against conflicts when two coverage runs happen simultaneously (pull 1220_). Thanks, Clément Pit-Claudel.

... (truncated)

Commits
  • 78a9c68 build: prep for 6.0.1
  • 72200e2 docs: this document isn't in a toc, and that's ok
  • a309f08 fix: make exceptions importable from coverage.misc again. #1226
  • f33b733 docs: note #1210 in the changelog
  • 19545b7 Fix an incompatibility with pyarmor
  • 613446c fix: pretend we didn't import third-party packages we use. #1228
  • 6211680 build: 3.10.0 is out
  • fb21f8e docs: the 5.0 change summary shouldn't be so prominent anymore
  • a5da277 build: bump version
  • 9515c4d docs: 6.0 sample HTML report
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [coverage](https://github.com/nedbat/coveragepy) from 5.3.1 to 6.0.1.
- [Release notes](https://github.com/nedbat/coveragepy/releases)
- [Changelog](https://github.com/nedbat/coveragepy/blob/master/CHANGES.rst)
- [Commits](nedbat/coveragepy@coverage-5.3.1...6.0.1)

---
updated-dependencies:
- dependency-name: coverage
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Oct 7, 2021
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Oct 12, 2021

Superseded by #45.

@dependabot dependabot bot closed this Oct 12, 2021
@dependabot dependabot bot deleted the dependabot/pip/coverage-6.0.1 branch October 12, 2021 08:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants