Update most test/lint dependencies #409
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==25.9.0→==25.12.0==7.9.1→==7.13.1==3.8.2→==3.10==1.3.7→==1.5.0==9.6.15→==9.7.1==0.29.1→==1.0.0==1.16.12→==2.0.1==1.16.1→==1.19.1>=0.10.3, <1→>=1.0.1, <2==1.1.402→==1.1.407==8.4.1→==9.0.2==1.0.0→==1.3.0==3.14.1→==3.15.1==0.14.2→==0.15.0==3.8.0.20250415→==3.10.0.20251106v1.19.0→v1.20.0Note: The
pre-commitmanager in Renovate is not supported by thepre-commitmaintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.Release Notes
psf/black (black)
v25.12.0Compare Source
Highlights
Stable style
# fmt: off/# fmt: onblocks were incorrectlyremoved, particularly affecting Jupytext's
# %% [markdown]comments (#4845)# fmt: skipcomments are used in a multi-part if-clause, onstring literals, or on dictionary entries with long lines (#4872)
fmt:directives aren't on the top level (#4856)Preview style
fmt: skipskipping the line after instead of the line it's on (#4855)magic trailing commas and intentional multiline formatting (#4865)
fix_fmt_skip_in_one_linerscrashing onwithstatements (#4853)fix_fmt_skip_in_one_linerscrashing on annotated parameters (#4854)# fmt: skipon them (#4894)Packaging
Integrations
output-fileinput to GitHub Actionpsf/blackto write formatter output to afile for artifact capture and log cleanliness (#4824)
v25.11.0Compare Source
Highlights
Stable style
# fmt: offand# fmt: onwere reformatted (#4811)being normalized (#4811)
Preview style
multiline_string_handlingfrom--unstableto--preview(#4760)comments (#4764)
# type: <value>(#4645)fix_fmt_skip_in_one_linerspreview feature to respect# fmt: skipfor compoundstatements with semicolon-separated bodies (#4800)
Configuration
no_cacheoption to control caching behavior. (#4803)Packaging
Output
(#4610)
Blackd
requests to blackd (#4774)
Integrations
psf/blackto support therequired-versionmajor-version-only"stability" format when using pyproject.toml (#4770)
coveragepy/coveragepy (coverage)
v7.13.1Compare Source
Added: the JSON report now includes a
"start_line"key for function andclass regions, indicating the first line of the region in the source. Closes
issue 2110_.Added: The
debug datacommand now takes file names as arguments on thecommand line, so you can inspect specific data files without needing to set
the
COVERAGE_FILEenvironment variable.Fix: the JSON report used to report module docstrings as executed lines,
which no other report did, as described in
issue 2105_. This is now fixed,thanks to Jianrong Zhao.
Fix: coverage.py uses a more disciplined approach to detecting where
third-party code is installed, and avoids measuring it. This shouldn't change
any behavior. If you find that it does, please get in touch.
Performance: data files that will be combined now record their hash as part
of the file name. This lets us skip duplicate data more quickly, speeding the
combining step.
Docs: added a section explaining more about what is considered a missing
branch and how it is reported: :ref:
branch_explain, as requested inissue 1597. Thanks toAyisha Mohammed <pull 2092_>.Tests: the test suite misunderstood what core was being tested if
COVERAGE_COREwasn't set on 3.14+. This is now fixed, closingissue 2109_... _issue 1597: #1597
.. _pull 2092: #2092
.. _issue 2105: #2105
.. _issue 2109: #2109
.. _issue 2110: #2110
.. _changes_7-13-0:
v7.13.0Compare Source
Feature: coverage.py now supports :file:
.coveragerc.tomlconfigurationfiles. These files use TOML syntax and take priority over
:file:
pyproject.tomlbut lower priority than :file:.coveragercfiles.Closes
issue 1643_ thanks toOlena Yefymenko <pull 1952_>_.Fix: we now include a permanent .pth file which is installed with the code,
fixing
issue 2084. In 7.12.1b1 this was done incorrectly: it didn't workwhen using the source wheel (
py3-none-any). This is now fixed. Thanks,Henry Schreiner <pull 2100_>.Deprecated: when coverage.py is installed, it creates three command entry
points:
coverage,coverage3, andcoverage-3.10(if installed forPython 3.10). The second and third of these are not needed and will
eventually be removed. They still work for now, but print a message about
their deprecation.
.. _issue 1643: #1643
.. _pull 1952: #1952
.. _pull 2100: #2100
.. _changes_7-12-1b1:
v7.12.0Compare Source
The HTML report now shows separate coverage totals for statements and
branches, as well as the usual combined coverage percentage. Thanks to Ryuta
Otsuka for the
discussion <issue 2081_>_ and theimplementation <pull 2085_>_.The JSON report now includes separate coverage totals for statements and
branches, thanks to
Ryuta Otsuka <pull 2090_>_.Fix:
except*clauses were not handled properly under the "sysmon"measurement core, causing KeyError exceptions as described in
issue 2086_.This is now fixed.
Fix: we now defend against aggressive mocking of
open()that could causeerrors inside coverage.py. An example of a failure is in
issue 2083_.Fix: in unusual cases where a test suite intentionally exhausts the system's
file descriptors to test handling errors in
open(), coverage.py wouldfail when trying to open source files, as described in
issue 2091_. Thisis now fixed.
A small tweak to the HTML report: file paths now use thin spaces around
slashes to make them easier to read.
.. _issue 2081: #2081
.. _issue 2083: #2083
.. _pull 2085: #2085
.. _issue 2086: #2086
.. _pull 2090: #2090
.. _issue 2091: #2091
.. _changes_7-11-3:
v7.11.3Compare Source
Fix: the 7.11.1 changes meant that conflicts between a requested measurement
core and other settings would raise an error. This was a breaking change from
previous behavior, as reported in
issue 2076_ andissue 2078_.The previous behavior has been restored: when the requested core conflicts
with other settings, another core is used instead, and a warning is issued.
For contributors: the repo has moved from Ned's
nedbat GitHub account_ tothe
coveragepy GitHub organization_. The default branch has changed frommaster to main.
.. _issue 2076: #2076
.. _issue 2078: #2078
.. _nedbat GitHub account: https://github.com/nedbat
.. _coveragepy GitHub organization: https://github.com/coveragepy
.. _changes_7-11-2:
v7.11.2Compare Source
Fix: using the "sysmon" measurement core in 7.11.1, if Python code was
claimed to come from a non-Python file, a
NotPythonexception could beraised. This could happen for example with Jinja templates compiled to
Python, as reported in
issue 2077_. This is now fixed.Doc: corrected the first entry in the 7.11.1 changelog.
.. _issue 2077: #2077
.. _changes_7-11-1:
v7.11.1Compare Source
Fix: some chanages to details of how the measurement core is chosen, and how
conflicting settings are handled. The "sysmon" core cannot be used with some
conurrency settings, with dynamic context, and in Python 3.12/3.13, with
branch measurement.
If the core is not specified and defaults to "sysmon" (Python 3.14+), but
other settings conflict with sysmon, then the "ctrace" core will be used
instead with no warning. For concurrency conflicts, this used to produce an
error, as described in
issue 2064_.If the "sysmon" core is explicitly requested in your configuration, but
other settings conflict, an error is now raised. This used to produce a
warning.
Fix: some multi-line case clauses or for loops (and probably other
constructs) could cause incorrect claims of missing branches with the
sys.monitoring core, as described in
issue 2070_. This is now fixed.Fix: when running in pytest under coverage, a
breakpoint()would stop inthe wrong frame, one level down from where it should, as described in
issue 1420_. This was due to a coverage change in v6.4.1 that seemed to give aslight performance improvement, but I couldn't reproduce the performance
gain, so it's been reverted, fixing the debugger problem.
A new debug option
--debug=coreshows which core is in use and why.Split
sqlitedebugging information out of thesys:ref:coverage debug <cmd_debug>and :ref:cmd_run_debugoptions since it's bulky and notvery useful.
Updated the :ref:
howitworkspage to better describe the three differentmeasurement cores.
.. _issue 1420: #1420
.. _issue 2064: #2064
.. _issue 2070: #2070
.. _changes_7-11-0:
v7.11.0Compare Source
.. _changes_7-10-7:
v7.10.7Compare Source
Performance: with branch coverage in large files, generating HTML, JSON, or
LCOV reports could take far too long due to some quadratic behavior when
creating the function and class index pages. This is now fixed, closing
issue 2048_. Thanks to Daniel Diniz for help diagnosing the problem.Most warnings and a few errors now have links to a page in the docs
explaining the specific message. Closes
issue 1921_... _issue 1921: #1921
.. _issue 2048: #2048
.. _changes_7-10-6:
v7.10.6Compare Source
Fix:
sourcedirectories were not properly communicated to subprocessesthat ran in different directories, as reported in
issue 1499_. This is nowfixed.
Performance:
Alex Gaynor continues fine-tuning <pull 2038_>_ the speed ofcombination, especially with many contexts.
.. _issue 1499: #1499
.. _pull 2038: #2038
.. _changes_7-10-5:
v7.10.5Compare Source
coverage combine: it's now about twice asfast! Huge thanks to Alex Gaynor for pull requests
2032 <pull 2032_>,2033 <pull 2033_>, and2034 <pull 2034_>_... _pull 2032: #2032
.. _pull 2033: #2033
.. _pull 2034: #2034
.. _changes_7-10-4:
v7.10.4Compare Source
Added
patch = forkfor times when the built-in forking support isinsufficient.
Fix:
patch = execvalso inherits the entire coverage configuration now... _changes_7-10-3:
v7.10.3Compare Source
Fixes for
patch = subprocess:If subprocesses spawned yet more subprocesses simultaneously, some coverage
could be missed. This is now fixed, closing
issue 2024_.If subprocesses were created in other directories, their data files were
stranded there and not combined into the totals, as described in
issue 2025_. This is now fixed.On Windows (or maybe only some Windows?) the patch would fail with a
ModuleNotFounderror trying to import coverage. This is now fixed,closing
issue 2022_.Originally only options set in the coverage configuration file would apply
to subprocesses. Options set on the
coverage runcommand line (such as--branch) wouldn't be communicated to the subprocesses. This couldlead to combining failures, as described in
issue 2021_. Now the entireconfiguration is used in subprocesses, regardless of its origin.
Added
debug=patchto help diagnose problems.Fix: really close all SQLite databases, even in-memory ones. Closes
issue 2017_... _issue 2017: #2017
.. _issue 2021: #2021
.. _issue 2022: #2022
.. _issue 2024: #2024
.. _issue 2025: #2025
.. _changes_7-10-2:
v7.10.2Compare Source
actually executed. This is now fixed, closing
issue 1999_. Python 3.9still shows the problem.
.. _issue 1999: #1999
.. _changes_7-10-1:
v7.10.1Compare Source
Fix: the exclusion for
if TYPE_CHECKING:was wrong: it marked the branchas partial, but it should have been a line exclusion so the entire clause
would be excluded. Improves
issue 831_.Fix: changed where .pth files are written for
patch = subprocess, closingissue 2006_... _issue 2006: #2006
.. _changes_7-10-0:
v7.10.0Compare Source
A new configuration option: ":ref:
config_run_patch" specifies named patchesto work around some limitations in coverage measurement. These patches are
available:
patch = _exitlets coverage save its data even when :func:os._exit() <python:os._exit>is used to abruptly end the process. This closeslong-standing
issue 310_ as well as its duplicates:issue 312,issue 1673,issue 1845, andissue 1941.patch = subprocessmeasures coverage in Python subprocesses createdwith :mod:
subprocess, :func:os.system, or one of the :func:execv <python:os.execl>or :func:spawnv <python:os.spawnl>family offunctions. Closes old
issue 367, its duplicateissue 378and oldissue 689_.patch = execvadjusts the :func:execv <python:os.execl>family offunctions to save coverage data before ending the current program and
starting the next. Not available on Windows. Closes
issue 43_ after 15years!
The HTML report now dimly colors subsequent lines in multi-line statements.
They used to have no color. This gives a better indication of the amount of
code missing in the report. Closes
issue 1308_.Two new exclusion patterns are part of the defaults:
...is automaticallyexcluded as a line and
if TYPE_CHECKING:is excluded as a branch. Closesissue 831_.A new command-line option:
--save-signal=USR1specifies a signal thatcoverage.py will listen for. When the signal is sent, the coverage data will
be saved. This makes it possible to save data from within long-running
processes. Thanks,
Arkady Gilinsky <pull 1998_>_.A new configuration option: ":ref:
config_report_partial_also" is a list ofregexes to add as pragmas for partial branches. This parallels the
":ref:
config_report_exclude_also" setting for adding line exclusionpatterns.
A few file path configuration settings didn't allow for tilde expansion:
:ref:
config_json_output, :ref:config_lcov_outputand:ref:
config_run_debug_file. This is now fixed.Wheels are included for 3.14 now that 3.14 rc1 is available.
We no longer ship a PyPy-specific wheel. PyPy will install the pure-Python
wheel. Closes
issue 2001_.In the very unusual situation of not having a current frame, coverage no
longer crashes when using the sysmon core, fixing
issue 2005_... _issue 43: #43
.. _issue 310: #310
.. _issue 312: #312
.. _issue 367: #367
.. _issue 378: #378
.. _issue 689: #689
.. _issue 831: #831
.. _issue 1308: #1308
.. _issue 1673: #1673
.. _issue 1845: #1845
.. _issue 1941: #1941
.. _pull 1998: #1998
.. _issue 2001: #2001
.. _issue 2005: #2005
.. _changes_7-9-2:
v7.9.2Compare Source
Fix: complex conditionals within a line might cause a KeyError when using
sys.monitoring, as reported in
issue 1991_. This is now fixed.Fix: we can now measure coverage for code in Python archive (.par) files.
Thanks,
Itamer Oren <pull 1984_>_... _pull 1984: #1984
.. _issue 1991: #1991
.. _changes_7-9-1:
Python-Markdown/markdown (markdown)
v3.10Compare Source
v3.9Compare Source
fralau/mkdocs_macros_plugin (mkdocs-macros-plugin)
v1.5.0Compare Source
v1.4.1Compare Source
requests(#269)v1.4.0Compare Source
v1.3.9Compare Source
squidfunk/mkdocs-material (mkdocs-material)
v9.7.1: mkdocs-material-9.7.1Compare Source
v9.7.0: mkdocs-material-9.7.0Compare Source
→ Read the full announcement on our blog
This release includes all features that were previously exclusive to the Insiders edition. These features are now freely available to everyone.
Note on deprecated plugins: The projects and typeset plugins are included in this release, but must be considered deprecated. Both plugins proved unsustainable to maintain and represent architectural dead ends. They are provided as-is without ongoing support.
Changes:
v9.6.23: mkdocs-material-9.6.23Compare Source
v9.6.22: mkdocs-material-9.6.22Compare Source
v9.6.21: mkdocs-material-9.6.21Compare Source
v9.6.20: mkdocs-material-9.6.20Compare Source
&character not escaped in search highlightingv9.6.19: mkdocs-material-9.6.19Compare Source
v9.6.18: mkdocs-material-9.6.18Compare Source
v9.6.17: mkdocs-material-9.6.17Compare Source
v9.6.16: mkdocs-material-9.6.16Compare Source
mkdocstrings/mkdocstrings (mkdocstrings)
v1.0.0Compare Source
Compare with 0.30.1
Breaking Changes
BaseHandler.name: Attribute value was changed:''-> unsetBaseHandler.domain: Attribute value was changed:''-> unsetBaseHandler.fallback_config: Public object was removedBaseHandler.__init__(args): Parameter was removedBaseHandler.__init__(kwargs): Parameter was removedBaseHandler.__init__(theme): Parameter was added as requiredBaseHandler.__init__(custom_templates): Parameter was added as requiredBaseHandler.__init__(mdx): Parameter was added as requiredBaseHandler.__init__(mdx_config): Parameter was added as requiredBaseHandler.update_env(args): Parameter was removedBaseHandler.update_env(kwargs): Parameter was removedBaseHandler.update_env(config): Parameter was added as requiredHandlers.get_anchors: Public object was removed (import frommkdocstringsdirectly)mkdocstrings.plugin: Public module was removed (import frommkdocstringsdirectly)mkdocstrings.loggers: Public module was removed (import frommkdocstringsdirectly)mkdocstrings.inventory: Public module was removed (import frommkdocstringsdirectly)mkdocstrings.extension: Public module was removed (import frommkdocstringsdirectly)mkdocstrings.handlers: Public module was removed (import frommkdocstringsdirectly)Code Refactoring
v0.30.1Compare Source
Compare with 0.30.0
Bug Fixes
v0.30.0Compare Source
Compare with 0.30.0
Bug Fixes
mkdocstrings/python (mkdocstrings-python)
v2.0.1Compare Source
Compare with 2.0.0
Bug Fixes
Code Refactoring
v2.0.0Compare Source
Compare with 1.19.0
Code Refactoring
v1.19.0Compare Source
Compare with 1.18.2
Features
__all__ordering feature (84aaebc by Timothée Mazzucotelli).Code Refactoring
v1.18.2Compare Source
Compare with 1.18.1
Bug Fixes
v1.18.1Compare Source
Compare with 1.18.0
Bug Fixes
__init__method whenoverloads_onlyis true and it is merged into the class (9ef620f by Timothée Mazzucotelli). Issue-308v1.18.0Compare Source
Compare with 1.17.0
Features
Bug Fixes
v1.17.0Compare Source
Compare with 1.16.12
Features
warn_missing_typesandwarnings(0e3bdb8 by Timothée Mazzucotelli). Issue-mkdocstrings-437skip_local_inventoryoption to prevent objects from being registered in the local objects inventory (e82c24f by Bartosz Sławecki). Issue-296, Issue-mkdocstrings-671, PR-297Code Refactoring
localeoption in favor of mkdocstrings' (17f71ba by Timothée Mazzucotelli). PR-288python/mypy (mypy)
v1.19.1Compare Source
types.NoneTypein match cases (A5rocks, PR 20383)v1.19.0Compare Source
v1.18.2Compare Source
object.__init__(Stephen Morton, PR 19733)v1.18.1Compare Source
We’ve just uploaded mypy 1.18.1 to the Python Package Index (PyPI).
Mypy is a static type checker for Python. This release includes new features, performance
improvements and bug fixes. You can install it as follows:
You can read the full documentation for this release on Read the Docs.
Mypy Performance Improvements
Mypy 1.18.1 includes numerous performance improvements, resulting in about 40% speedup
compared to 1.17 when type checking mypy itself. In extreme cases, the improvement
can be 10x or higher. The list below is an overview of the various mypy optimizations.
Many mypyc improvements (discussed in a separate section below) also improve performance.
Type caching optimizations have a small risk of causing regressions. When
reporting issues with unexpected inferred types, please also check if
--disable-expression-cachewill work around the issue, as it turns off some ofthese optimizations.
Configuration
📅 Schedule: Branch creation - "every 3 months on the first day of the month" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.