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

Update dependency coverage to v5.5 #28

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 17, 2020

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
coverage ==5.0.3 -> ==5.5 age adoption passing confidence

Release Notes

nedbat/coveragepy

v5.5

Compare Source

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

.. _issue 803:https://github.com/nedbat/coveragepy/issues/8033
.. _issue 955https://github.com/nedbat/coveragepy/issues/95555
.. _issue 106https://github.com/nedbat/coveragepy/issues/1065065
.. _issue 11https://github.com/nedbat/coveragepy/issues/11081108
.. _pull request 1https://github.com/nedbat/coveragepy/pull/1110/1110
.. _issue https://github.com/nedbat/coveragepy/issues/1123s/1123
.. _issuehttps://github.com/nedbat/coveragepy/issues/1124es/1124

.. _changes_54:

v5.4

Compare Source

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

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

.. _issue 577:https://github.com/nedbat/coveragepy/issues/5777
.. _issue 732https://github.com/nedbat/coveragepy/issues/73232
.. _issue 92https://github.com/nedbat/coveragepy/issues/922922
.. _issue 10https://github.com/nedbat/coveragepy/issues/10841084
.. _issue 1https://github.com/nedbat/coveragepy/issues/1086/1086
.. _issue https://github.com/nedbat/coveragepy/issues/1090s/1090
.. _phttps://github.com/nedbat/coveragepy/pull/1080ll/1080
.. _pep626: https://www.python.org/dev/peps/pep-0626/

.. _changes_531:

v5.3.1

Compare Source

  • When using --source on a large source tree, v5.x was slower than previous
    versions. This performance regression is now fixed, closing issue 1037_.

  • Mysterious SQLite errors can happen on PyPy, as reported in issue 1010_. An
    immediate retry seems to fix the problem, although it is an unsatisfying
    solution.

  • The HTML report now saves the sort order in a more widely supported way,
    fixing issue 986. Thanks, Sebastián Ramírez (pull request 1066).

  • The HTML report pages now have a :ref:Sleepy Snake <sleepy> favicon.

  • Wheels are now provided for manylinux2010, and for PyPy3 (pp36 and pp37).

  • Continuous integration has moved from Travis and AppVeyor to GitHub Actions.

.. _issue 986:https://github.com/nedbat/coveragepy/issues/9866
.. _issue 1037https://github.com/nedbat/coveragepy/issues/103737
.. _issue 101https://github.com/nedbat/coveragepy/issues/1010010
.. _pull request 10https://github.com/nedbat/coveragepy/pull/10661066

.. _changes_53:

v5.3

Compare Source

  • When using --source on a large source tree, v5.x was slower than previous
    versions. This performance regression is now fixed, closing issue 1037_.

  • Mysterious SQLite errors can happen on PyPy, as reported in issue 1010_. An
    immediate retry seems to fix the problem, although it is an unsatisfying
    solution.

  • The HTML report now saves the sort order in a more widely supported way,
    fixing issue 986. Thanks, Sebastián Ramírez (pull request 1066).

  • The HTML report pages now have a :ref:Sleepy Snake <sleepy> favicon.

  • Wheels are now provided for manylinux2010, and for PyPy3 (pp36 and pp37).

  • Continuous integration has moved from Travis and AppVeyor to GitHub Actions.

.. _issue 986:https://github.com/nedbat/coveragepy/issues/9866
.. _issue 1037https://github.com/nedbat/coveragepy/issues/103737
.. _issue 101https://github.com/nedbat/coveragepy/issues/1010010
.. _pull request 10https://github.com/nedbat/coveragepy/pull/10661066

.. _changes_53:

v5.2.1

Compare Source

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

v5.2

Compare Source

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

v5.1

Compare Source

  • The JSON report now includes counts of covered and missing branches. Thanks, Salvatore Zagaria.
  • On Python 3.8, try-finally-return reported wrong branch coverage with decorated async functions (issue 964). This is now fixed. Thanks, Kjell Braden.
  • The get_option() and set_option() methods can now manipulate the [paths] configuration setting. Thanks to Bernát Gábor for the fix for issue 967.

v5.0.4

Compare Source

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@pull-assistant
Copy link

pull-assistant bot commented Mar 17, 2020

Score: 1.00

Best reviewed: commit by commit


Optimal code review plan

     Update dependency coverage to v5.2.1

Powered by Pull Assistant. Last update 5a232be ... 5a232be. Read the comment docs.

@renovate renovate bot changed the title Update dependency coverage to v5.0.4 Update dependency coverage to v5.1 Apr 12, 2020
@renovate renovate bot changed the title Update dependency coverage to v5.1 Update dependency coverage to v5.2 Jul 10, 2020
@renovate renovate bot changed the title Update dependency coverage to v5.2 Update dependency coverage to v5.2.1 Aug 27, 2020
@renovate renovate bot changed the title Update dependency coverage to v5.2.1 Update dependency coverage to v5.3 Oct 29, 2020
@renovate renovate bot changed the title Update dependency coverage to v5.3 Update dependency coverage to v5.3.1 Jan 6, 2021
@renovate renovate bot changed the title Update dependency coverage to v5.3.1 Update dependency coverage to v5.4 Jan 30, 2021
@renovate renovate bot changed the title Update dependency coverage to v5.4 Update dependency coverage to v5.5 Apr 26, 2021
@renovate
Copy link
Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant