Update all dependencies #284
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
for more information, see https://pre-commit.ci
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #284 +/- ##
=======================================
Coverage 76.95% 76.95%
=======================================
Files 31 31
Lines 4530 4530
Branches 321 321
=======================================
Hits 3486 3486
Misses 975 975
Partials 69 69 🚀 New features to boost your workflow:
|
Contributor
Author
Edited/Blocked NotificationRenovate 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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
==2.16.0->==2.17.0==2024.8.30->==2024.12.14==3.4.0->==3.4.4==7.6.4->==7.12.0==0.18.1->==0.22.3==3.10->==3.11==2.0.0->==2.3.0==3.0.2->==3.0.3==3.23.1->==3.26.1==1.5.0->==1.6.0==2.9.2->==2.12.4==2.23.4->==2.41.5==2.18.0->==2.19.2==8.3.3->==8.4.2==3.14.0->==3.15.1==6.0.2->==6.0.3==2.1.0->==2.3.0==4.12.2->==4.15.0==1.8.0->==1.9.0==3.1->==3.2Release Notes
python-babel/babel (babel)
v2.17.0Compare Source
Happy 2025! This release is being made from FOSDEM 2025, in Brussels, Belgium.
Thank you to all contributors, new and old,
and here's to another great year of internationalization and localization!
Features
parse_timetime formats by @tomasr8 in :gh:1141str.indexwithstr.findby @tomasr8 in :gh:1130/etc/localtimeby @akx in :gh:11651179locale=Noneby @akx in :gh:1164Catalog.__setitem__by @tomasr8 in :gh:1167112611351132read_mologic regardingcatalog.charsetby @tomasr8 in :gh:11481121Deprecation and compatibility
Locale.number_symbolswill now have first-level keys for each numbering system.Since the implicit default numbering system still is
"latn", what had previouslybeen e.g.
Locale.number_symbols['decimal']is nowLocale.number_symbols['latn']['decimal'].distutilsorsetuptools; if you had beenusing the Babel setuptools command extensions, you would need to explicitly depend on
setuptools–though given you're running
setup.pyyou probably already do.Features
10451046certifi/python-certifi (certifi)
v2024.12.14Compare Source
jawah/charset_normalizer (charset-normalizer)
v3.4.4Compare Source
Changed
setuptoolsto a specific constraintsetuptools>=68,<=81.Removed
setuptools-scmas a build dependency.Misc
dev-requirements.txtand createdci-requirements.txtfor security purposes.multiple.intoto.jsonlin GitHub releases in addition to individual attestation file per wheel.v3.4.3Compare Source
Changed
CHARSET_NORMALIZER_USE_MYPYCisn't set to1. (#595) (#583)detectoutput legacy function. (#391)Added
Fixed
Misc
Each published wheel comes with its SBOM. We choose CycloneDX as the format.
v3.4.2Compare Source
Fixed
argparse.FileTypeby backporting the target class into the package. (#591)Changed
v3.4.1Compare Source
Changed
pyproject.tomlinstead ofsetup.cfgusing setuptools as the build backend.Added
Removed
build-requirements.txtas per usingpyproject.tomlnative build configuration.bin/integration.pyandbin/serve.pyin favor of downstream integration test (see noxfile).setup.cfgin favor ofpyproject.tomlmetadata configuration.utils.range_scanfunction.Fixed
utf_8instead of preferredutf-8. (#572)coveragepy/coveragepy (coverage)
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:
v7.9.1Compare Source
The "no-ctracer" warning is not issued for Python pre-release versions.
Coverage doesn't ship compiled wheels for those versions, so this was far too
noisy.
On Python 3.14+, the "sysmon" core is now the default if it's supported for
your configuration. Plugins and dynamic contexts are still not supported
with it.
.. _changes_7-9-0:
v7.9.0Compare Source
Added a
[run] coreconfiguration setting to specify the measurement core,which was previously only available through the COVERAGE_CORE environment
variable. Finishes
issue 1746_.Fixed incorrect rendering of f-strings with doubled braces, closing
issue 1980_.If the C tracer core can't be imported, a warning ("no-ctracer") is issued
with the reason.
The C tracer core extension module now conforms to
PEP 489, closingissue 1977. Thanks,Adam Turner <pull 1978_>_.Fixed a "ValueError: min() arg is an empty sequence" error caused by strange
empty modules, found by
oss-fuzz_... _issue 1746: #1746
.. _issue 1977: #1977
.. _pull 1978: #1978
.. _issue 1980: #1980
.. _PEP 489: https://peps.python.org/pep-0489
.. _oss-fuzz: https://google.github.io/oss-fuzz/
.. _changes_7-8-2:
v7.8.2Compare Source
Thanks,
Finn Womack <pull 1972_>_... _issue 1971: #1971
.. _pull 1972: #1972
.. _changes_7-8-1:
v7.8.1Compare Source
A number of EncodingWarnings were fixed that could appear if you've enabled
PYTHONWARNDEFAULTENCODING, fixing
issue 1966. Thanks,Henry Schreiner <pull 1967_>.Fixed a race condition when using sys.monitoring with free-threading Python,
closing
issue 1970_... _issue 1966: #1966
.. _pull 1967: #1967
.. _issue 1970: #1970
.. _changes_7-8-0:
v7.8.0Compare Source
Added a new
source_dirssetting for symmetry with the existingsource_pkgssetting. It's preferable to the existingsourcesetting,because you'll get a clear error when directories don't exist. Fixes
issue 1942. Thanks,Jeremy Fleischman <pull 1943_>.Fix: the PYTHONSAFEPATH environment variable new in Python 3.11 is properly
supported, closing
issue 1696. Thanks,Philipp A. <pull 1700_>. Thisworks properly except for a detail when using the
coveragecommand onWindows. There you can use
python -m coverageinstead if you need exactemulation.
.. _issue 1696: #1696
.. _pull 1700: #1700
.. _issue 1942: #1942
.. _pull 1943: #1943
.. _changes_7-7-1:
v7.7.1Compare Source
test!
.. _changes_7-7-0:
v7.7.0Compare Source
The Coverage object has a new method, :meth:
.Coverage.branch_statsforgetting simple branch information for a module. Closes
issue 1888_.The :class:
Coverage constructor<.Coverage>now has apluginsparameterfor passing in plugin objects directly, thanks to
Alex Gaynor <pull 1919_>_.Many constant tests in if statements are now recognized as being optimized
away. For example, previously
if 13:would have been considered a branchwith one path not taken. Now it is understood as always true and no coverage
is missing.
The experimental sys.monitoring support now works for branch coverage if you
are using Python 3.14.0 alpha 6 or newer. This should reduce the overhead
coverage.py imposes on your test suite. Set the environment variable
COVERAGE_CORE=sysmonto try it out.Confirmed support for PyPy 3.11. Thanks Michał Górny.
.. _issue 1888: #1888
.. _pull 1919: #1919
.. _changes_7-6-12:
v7.6.12Compare Source
issue 1927_). These are nowbuilding reliably.
.. _issue 1927: #1927
.. _changes_7-6-11:
v7.6.11Compare Source
Fix: a memory leak in CTracer has been fixed. The details are in
issue 1924_ andpytest-dev 676_. This should reduce the memory footprint foreveryone even if it hadn't caused a problem before.
We now ship a py3-none-any.whl wheel file. Thanks,
Russell Keith-Magee <pull 1914_>_... _pull 1914: #1914
.. _issue 1924: #1924
.. _pytest-dev 676: pytest-dev/pytest-cov#676
.. _changes_7-6-10:
v7.6.10Compare Source
Fix: some descriptions of missing branches in HTML and LCOV reports were
incorrect when multi-line statements were involved (
issue 1874_ andissue 1875_). These are now fixed.Fix: Python 3.14
defers evaluation of annotations <pep649_>_ by moving theminto separate code objects. That code is rarely executed, so coverage.py
would mark them as missing, as reported in
issue 1908_. Now they areignored by coverage automatically.
Fixed an obscure and mysterious problem on PyPy 3.10 seemingly involving
mocks, imports, and trace functions:
issue 1902_. To be honest, I don'tunderstand the problem or the solution, but
git bisecthelped find it,and now it's fixed.
Docs: re-wrote the :ref:
subprocesspage to put multiprocessing first and tohighlight the correct use of :class:
multiprocessing.Pool <python:multiprocessing.pool.Pool>... _issue 1874: #1874
.. _issue 1875: #1875
.. _issue 1902: #1902
.. _issue 1908: #1908
.. _pep649: https://docs.python.org/3.14/whatsnew/3.14.html#whatsnew314-deferred-annotations
.. _changes_7-6-9:
v7.6.9Compare Source
Tomas Uribe fixed <pull 1901_>_ a performance problem in the XMLreport. Large code bases should produce XML reports much faster now.
.. _pull 1901: #1901
.. _changes_7-6-8:
v7.6.8Compare Source
Fix: the LCOV report code assumed that a branch line that took no branches
meant that the entire line was unexecuted. This isn't true in a few cases:
the line might always raise an exception, or might have been optimized away.
Fixes
issue 1896_.Fix: similarly, the HTML report will now explain that a line that jumps to
none of its expected destinations must have always raised an exception.
Previously, it would say something nonsensical like, "line 4 didn't jump to
line 5 because line 4 was never true, and it didn't jump to line 7 because
line 4 was always true." This was also shown in
issue 1896_... _issue 1896: #1896
.. _changes_7-6-7:
v7.6.7Compare Source
so it's been restored to a conditional. Sorry for the churn.
.. _changes_7-6-6:
v7.6.6Compare Source
reported in
issue 1891_. The assert has been removed... _issue 1891: #1891
.. _changes_7-6-5:
v7.6.5Compare Source
Fix: fine-tuned the exact Python version (3.12.6) when exiting from
withstatements changed how they traced. This affected whether people saw the
fix for
issue 1880_.Fix: isolate our code more from mocking in the os module that in rare cases
can cause
bizarre behavior <pytest-cov-666_>_.Refactor: some code unreachable code paths in parser.py were changed to
asserts. If you encounter any of these, please let me know!
.. _pytest-cov-666: pytest-dev/pytest-cov#666
.. _changes_7-6-4:
kjd/idna (idna)
v3.11pytest-dev/iniconfig (iniconfig)
v2.3.0=====
v2.2.0=====
v2.1.0Compare Source
=====
pallets/markupsafe (markupsafe)
v3.0.3Compare Source
Released 2025-09-27
__version__raisesDeprecationWarninginstead ofUserWarning.:issue:
487489) for the C extension.:issue:
494485503505marshmallow-code/marshmallow (marshmallow)
v3.26.1Compare Source
v3.26.0Compare Source
v3.25.1Compare Source
v3.25.0Compare Source
v3.24.2Compare Source
v3.24.1Compare Source
v3.24.0Compare Source
v3.23.3Compare Source
v3.23.2Compare Source
pydantic/pydantic (pydantic)
v2.12.4Compare Source
v2.12.3Compare Source
GitHub release
What's Changed
This is the third 2.13 patch release, fixing issues related to the
FieldInfoclass, and reverting a change to the supportedafter model validator function signatures.
Starting in 2.12.0, using class methods for after model validators raised an error, but the error wasn't raised concistently. We decided
to emit a deprecation warning instead.
FieldInfo.asdict()method, improve documentation aroundFieldInfoby @Viicos in #12411.This also add back support for mutations on
FieldInfoclasses, that are reused asAnnotatedmetadata. However, note that this is stillnot a supported pattern. Instead, please refer to the added example in the documentation.
The blog post section on changes was also updated to document the changes related to
serialize_as_any.v2.12.2Compare Source
GitHub release
What's Changed
Fixes
pydantic-coreversion, as a corrupted CPython 3.10manylinux2014_aarch64wheel got uploaded (pydantic-core#1843).v2.12.1Compare Source
GitHub release
What's Changed
This is the first 2.12 patch release
Configuration
📅 Schedule: Branch creation - "after 7am and before 4pm on monday" in timezone Europe/London, 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.