search

omnilib / aiosqlite

asyncio bridge to the standard sqlite3 module
https://aiosqlite.omnilib.dev
MIT License
1.17k stars 93 forks source link

Bump coverage[toml] from 6.5.0 to 7.1.0 #220

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps coverage[toml] from 6.5.0 to 7.1.0.

Release notes

Sourced from coverage[toml]'s releases.

7.1.0

  • Added: the debug output file can now be specified with [run] debug_file in the configuration file. Closes issue 1319.
  • Performance: fixed a slowdown with dynamic contexts that's been around since 6.4.3. The fix closes issue 1538. Thankfully this doesn't break the Cython change that fixed issue 972. Thanks to Mathieu Kniewallner for the deep investigative work and comprehensive issue report.
  • Typing: all product and test code has type annotations.

:arrow_right:  PyPI page: coverage 7.1.0. :arrow_right:  To install: python3 -m pip install coverage==7.1.0

7.0.5

  • Fix: On Python 3.7, a file with type annotations but no from __future__ import annotations would be missing statements in the coverage report. This is now fixed, closing issue 1524.

:arrow_right:  PyPI page: coverage 7.0.5. :arrow_right:  To install: python3 -m pip install coverage==7.0.5

7.0.4

  • Performance: an internal cache of file names was accidentally disabled, resulting in sometimes drastic reductions in performance. This is now fixed, closing issue 1527. Thanks to Ivan Ciuvalschii for the reproducible test case.

:arrow_right:  PyPI page: coverage 7.0.4. :arrow_right:  To install: python3 -m pip install coverage==7.0.4

7.0.3

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

:arrow_right:  PyPI page: coverage 7.0.3. :arrow_right:  To install: python3 -m pip install coverage==7.0.3

7.0.2

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

:arrow_right:  PyPI page: coverage 7.0.2. :arrow_right:  To install: python3 -m pip install coverage==7.0.2

7.0.1

  • When checking if a file mapping resolved to a file that exists, we weren’t considering files in .whl files. This is now fixed, closing issue 1511.
  • File pattern rules were too strict, forbidding plus signs and curly braces in directory and file names. This is now fixed, closing issue 1513.
  • Unusual Unicode or control characters in source files could prevent reporting. This is now fixed, closing issue 1512.
  • The PyPy wheel now installs on PyPy 3.7, 3.8, and 3.9, closing issue 1510.

:arrow_right:  PyPI page: coverage 7.0.1. :arrow_right:  To install: python3 -m pip install coverage==7.0.1

... (truncated)

Changelog

Sourced from coverage[toml]'s changelog.

Version 7.1.0 — 2023-01-24

  • Added: the debug output file can now be specified with [run] debug_file in the configuration file. Closes issue 1319_.

  • Performance: fixed a slowdown with dynamic contexts that's been around since 6.4.3. The fix closes issue 1538. Thankfully this doesn't break the Cython change that fixed issue 972_. Thanks to Mathieu Kniewallner for the deep investigative work and comprehensive issue report.

  • Typing: all product and test code has type annotations.

.. _Cython change: nedbat/coveragepy#1347 .. _issue 972: nedbat/coveragepy#972 .. _issue 1319: nedbat/coveragepy#1319 .. _issue 1538: nedbat/coveragepy#1538

.. _changes_7-0-5:

Version 7.0.5 — 2023-01-10

  • Fix: On Python 3.7, a file with type annotations but no from __future__ import annotations would be missing statements in the coverage report. This is now fixed, closing issue 1524_.

.. _issue 1524: nedbat/coveragepy#1524

.. _changes_7-0-4:

Version 7.0.4 — 2023-01-07

  • Performance: an internal cache of file names was accidentally disabled, resulting in sometimes drastic reductions in performance. This is now fixed, closing issue 1527_. Thanks to Ivan Ciuvalschii for the reproducible test case.

.. _issue 1527: nedbat/coveragepy#1527

.. _changes_7-0-3:

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

... (truncated)

Commits
  • 32fd81e docs: sample HTML for 7.1.0
  • 36712f4 docs: prep for 7.1.0
  • 4cc3292 perf: avoid needless sql operations. #1538
  • 674204f test: more flexibility in setting a static context locally
  • 61f6ee5 fix: make tracing messages easier to understand
  • e1ae48e test: more tests of debug output control
  • ff127f8 build: igor tweaks for scriv start marker
  • 5f65d87 feat: the debug output file can be specified in the config file. #1319
  • c51ac46 docs: explain how to use --debug=trace
  • 82c2638 chore: make upgrade to get eventlet 0.33.3
  • 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 #223.