search

mv / fundamentus-api

Python/Pandas code to perform fundamental analysis on companies listed on BOVESPA from the website Fundamentus (www.fundamentus.com.br)
MIT License
90 stars 35 forks source link

Bump coverage from 5.3.1 to 7.0.3 #114

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps coverage from 5.3.1 to 7.0.3.

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 7.0.3 — 2023-01-03

  • Fix: when using pytest-cov or pytest-xdist, or perhaps both, the combining step could fail with assert row is not None using 7.0.2. This was due to a race condition that has always been possible and is still possible. In 7.0.1 and before, the error was silently swallowed by the combining code. Now it will produce a message "Couldn't combine data file" and ignore the data file as it used to do before 7.0.2. Closes issue 1522_.

.. _issue 1522: nedbat/coveragepy#1522

.. _changes_7-0-2:

Version 7.0.2 — 2023-01-02

  • Fix: when using the [run] relative_files = True setting, a relative [paths] pattern was still being made absolute. This is now fixed, closing issue 1519_.

  • Fix: if Python doesn't provide tomllib, then TOML configuration files can only be read if coverage.py is installed with the [toml] extra. Coverage.py will raise an error if TOML support is not installed when it sees your settings are in a .toml file. But it didn't understand that [tools.coverage] was a valid section header, so the error wasn't reported if you used that header, and settings were silently ignored. This is now fixed, closing issue 1516_.

  • Fix: adjusted how decorators are traced on PyPy 7.3.10, fixing issue 1515_.

  • Fix: the coverage lcov report did not properly implement the --fail-under=MIN option. This has been fixed.

  • Refactor: added many type annotations, including a number of refactorings. This should not affect outward behavior, but they were a bit invasive in some places, so keep your eyes peeled for oddities.

  • Refactor: removed the vestigial and long untested support for Jython and IronPython.

.. _issue 1515: nedbat/coveragepy#1515 .. _issue 1516: nedbat/coveragepy#1516 .. _issue 1519: nedbat/coveragepy#1519

.. _changes_7-0-1:

Version 7.0.1 — 2022-12-23

... (truncated)

Commits
  • 2ff9098 docs: prep for 7.0.3
  • 1f34d8b fix: race condition on data file shouldn't break combining. #1522
  • 85170bf build: two-step combines for speed
  • 1605f07 mypy: misc.py, test_misc.py
  • 4f3ccf2 refactor: a better way to have maybe-importable third-party modules
  • 98301ed mypy: test_config.py, test_context.py
  • 9d2e1b0 mypy: test_concurrency.py, test_python.py
  • c3ee30c refactor(test): use tmp_path instead of tmpdir
  • 0b05b45 mypy: test_annotate.py test_arcs.py test_collector.py
  • 2090f79 style: better
  • 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[bot] commented 1 year ago

Superseded by #115.