Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 16, 2020

Bumps coverage from 4.5.3 to 5.3.

Release notes

Sourced from coverage's releases.

coverage-5.3

  • The source setting has always been interpreted as either a file path or a module, depending on which existed. If both interpretations were valid, it was assumed to be a file path. The new source_pkgs setting can be used to name a package to disambiguate this case. Thanks, Thomas Grainger. Fixes issue 268.
  • If a plugin was disabled due to an exception, we used to still try to record its information, causing an exception, as reported in issue 1011. This is now fixed.

coverage-5.2.1

  • The dark mode HTML report still used light colors for the context listing, making them unreadable (issue 1009). This is now fixed.
  • The time stamp on the HTML report now includes the time zone. Thanks, Xie Yanbo (pull request 960).

coverage-5.2

  • The HTML report has been redesigned by Vince Salvino. There is now a dark mode, the code text is larger, and system sans serif fonts are used, in addition to other small changes (issue 858 and pull request 931).
  • The coverage report and coverage html commands now accept a --precision option to control the number of decimal points displayed. Thanks, Teake Nutma (pull request 982).
  • The coverage report and coverage html commands now accept a --no-skip-covered option to negate --skip-covered. Thanks, Anthony Sottile (issue 779 and pull request 932).
  • The --skip-empty option is now available for the XML report, closing issue 976.
  • The coverage report command now accepts a --sort option to specify how to sort the results. Thanks, Jerin Peter George (pull request 1005).
  • If coverage fails due to the coverage total not reaching the --fail-under value, it will now print a message making the condition clear. Thanks, Naveen Yadav (pull request 977).
  • TOML configuration files with non-ASCII characters would cause errors on Windows (issue 990). This is now fixed.
  • The output of --debug=trace now includes information about how the --source option is being interpreted, and the module names being considered.

coverage-5.1

coverage-5.0.4

  • If using the [run] relative_files setting, the XML report will use relative files in the <source> elements indicating the location of source code. Closes issue 948.
  • The textual summary report could report missing lines with negative line numbers on PyPy3 7.1 (issue 943). This is now fixed.
  • Windows wheels for Python 3.8 were incorrectly built, but are now fixed. (issue 949)
  • Updated Python 3.9 support to 3.9a4.
  • HTML reports couldn’t be sorted if localStorage wasn’t available. This is now fixed: sorting works even though the sorting setting isn’t retained. (issue 944 and pull request 945). Thanks, Abdeali Kothari.

coverage-5.0.3

  • A performance improvement in 5.0.2 didn’t work for test suites that changed directory before combining data, causing “Couldn’t use data file: no such table: meta” errors (issue 916). This is now fixed.
  • Coverage could fail to run your program with some form of “ModuleNotFound” or “ImportError” trying to import from the current directory. This would happen if coverage had been packaged into a zip file (for example, on Windows), or was found indirectly (for example, by pyenv-virtualenv). A number of different scenarios were described in issue 862 which is now fixed. Huge thanks to Agbonze O. Jeremiah for reporting it, and Alexander Waters and George-Cristian Bîrzan for protracted debugging sessions.
  • Added the “premain” debug option.
  • Added SQLite compile-time options to the “debug sys” output.

coverage-5.0.2

  • Programs that used multiprocessing and changed directories would fail under coverage. This is now fixed (issue 890). A side effect is that debug information about the config files read now shows absolute paths to the files.
  • When running programs as modules (coverage run -m) with --source, some measured modules were imported before coverage starts. This resulted in unwanted warnings (“Already imported a file that will be measured”) and a reduction in coverage totals (issue 909). This is now fixed.
  • If no data was collected, an exception about “No data to report” could happen instead of a 0% report being created (issue 884). This is now fixed.
  • The handling of source files with non-encodable file names has changed. Previously, if a file name could not be encoded as UTF-8, an error occurred, as described in issue 891. Now, those files will not be measured, since their data would not be recordable.
  • A new warning (“dynamic-conflict”) is issued if two mechanisms are trying to change the dynamic context. Closes issue 901.
  • coverage run --debug=sys would fail with an AttributeError. This is now fixed (issue 907).

coverage-5.0.1

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

... (truncated)

Changelog

Sourced from coverage's changelog.

Version 5.3 --- 2020-09-13

  • The source setting has always been interpreted as either a file path or a module, depending on which existed. If both interpretations were valid, it was assumed to be a file path. The new source_pkgs setting can be used to name a package to disambiguate this case. Thanks, Thomas Grainger. Fixes issue 268_.

  • If a plugin was disabled due to an exception, we used to still try to record its information, causing an exception, as reported in issue 1011_. This is now fixed.

.. _issue 268: nedbat/coveragepy#268 .. _issue 1011: nedbat/coveragepy#1011

.. _changes_521:

Version 5.2.1 --- 2020-07-23

  • The dark mode HTML report still used light colors for the context listing, making them unreadable (issue 1009_). This is now fixed.

  • The time stamp on the HTML report now includes the time zone. Thanks, Xie Yanbo (pull request 960_).

.. _pull request 960: nedbat/coveragepy#960 .. _issue 1009: nedbat/coveragepy#1009

.. _changes_52:

Version 5.2 --- 2020-07-05

  • The HTML report has been redesigned by Vince Salvino. There is now a dark mode, the code text is larger, and system sans serif fonts are used, in addition to other small changes (issue 858_ and pull request 931_).

  • The coverage report and coverage html commands now accept a --precision option to control the number of decimal points displayed. Thanks, Teake Nutma (pull request 982_).

  • The coverage report and coverage html commands now accept a --no-skip-covered option to negate --skip-covered. Thanks, Anthony Sottile (issue 779_ and pull request 932_).

  • The --skip-empty option is now available for the XML report, closing

... (truncated)

Commits
  • d13594e Making a release
  • 039ef09 If a plugin is disabled, don't try to record its file tracers. #1011
  • 24eb6fd Move disable_plugin to Python
  • 987ceb9 Fix a missed exception handling for bad plugins
  • c907b2e ambigious -> ambiguous
  • 263f3e1 Docs and cleanup for source_pkgs
  • ecd6ab1 Create Way to force package even if filepath exists (#1026)
  • 39e6d1d Thomas Grainger's first commit
  • 154f528 replace confusing comment with assertion (#1028)
  • c315908 Explain a mystery
  • 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)

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Dec 16, 2020
@codecov-io
Copy link

codecov-io commented Dec 16, 2020

Codecov Report

Merging #169 (31911d5) into develop (2d9ba1e) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop     #169   +/-   ##
========================================
  Coverage    78.14%   78.14%           
========================================
  Files           26       26           
  Lines         1725     1725           
  Branches       279      279           
========================================
  Hits          1348     1348           
  Misses         256      256           
  Partials       121      121           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2d9ba1e...31911d5. Read the comment docs.

@jtrh jtrh self-assigned this Dec 16, 2020
@jtrh jtrh merged commit a7a78e1 into develop Dec 16, 2020
@jtrh jtrh deleted the dependabot/pip/coverage-5.3 branch December 16, 2020 15:09
@jtrh jtrh mentioned this pull request Jan 11, 2021
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.

3 participants