SAP / pylint-per-file-ignores / 33449646952

98%

push

github

Update dependency coverage to v7.16.0 (#288)

This PR contains the following updates:

| Package | Change |
[Age](https://docs.renovatebot.com/merge-confidence/) |
[Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
| [coverage](https://redirect.github.com/coveragepy/coveragepy) |
`==7.15.4` → `==7.16.0` |
![age](https://developer.mend.io/api/mc/badges/age/pypi/coverage/7.16.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/coverage/7.15.4/7.16.0?slim=true)
|

---

### Release Notes

<details>
<summary>coveragepy/coveragepy (coverage)</summary>

###
[`v7.16.0`](https://redirect.github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7160--2026-08-28)

[Compare
Source](https://redirect.github.com/coveragepy/coveragepy/compare/7.15.4...7.16.0)

- When combining files, now path separator slashes will automatically be
converted to the local file system style. This makes it less necessary
to
define `[paths]` configuration to combine data across operating systems.
  Fixes `issue 2266`\_.

- The :meth:`.Coverage.switch_context` method now returns the previous
context.

- Fix: previously, a `[paths]` pattern would be replaced everywhere in a
file
path when it was only meant to be replaced once, in the leading portion
of
  the path. This is now fixed, in `pull 2268`\_.

- Fixes to validation of options and configuration settings:

- Negative precision settings now always cause useful error messages
(`pull
    2261`\_).

  - An invalid regex in the `--contexts` option (or the `[report]
    contexts` setting) reported a confusing "Couldn't use data file ...:
user-defined function raised exception" error. Now it raises a proper
configuration error naming the bad regex, like other regex settings do
    (`pull 2262`\_).

- Non-string values in TOML configuration settings now produce a helpful
error message instead of a traceback. This affects list settings whose
elements aren't strings (like `om... (continued)

32 of 34 branches covered (94.12%)

Branch coverage included in aggregate %.

168 of 171 relevant lines covered (98.25%)

0.98 hits per line