Update all dependencies #97
Open
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
638d809 to
7ee0d22
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all
branch
from
7ee0d22 to
16eb219
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all
branch
from
16eb219 to
2729cba
Compare
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: python/Pipfile.lock |
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
54a80ed to
c3abada
Compare
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
24404c8 to
a4cff8f
Compare
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
4050065 to
ce8e468
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
ce8e468 to
f4f40d1
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
e6cd350 to
97ad580
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
bdf3e30 to
61bcc61
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
00d9866 to
27678af
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
8c8cf1d to
d49789c
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
d49789c to
900d7fb
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
900d7fb to
61b5921
Compare
renovate
bot
force-pushed
the
renovate/all
branch
5 times, most recently
from
6d72453 to
357b729
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
bdfebf4 to
d567f4e
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
aee017f to
899c41e
Compare
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
b0d8777 to
e74381e
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
362ca35 to
fb85686
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
fb85686 to
d5783d3
Compare
renovate
bot
force-pushed
the
renovate/all
branch
6 times, most recently
from
02ec020 to
85979e3
Compare
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
b0a0f5a to
66f7569
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
66f7569 to
a273521
Compare
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:
==7.3.2->==7.6.12==6.1.0->==7.1.2v1.1.0->v1.2.1v1.60.1->v1.64.51.23.0-bullseye->1.24.0-bullseye==7.4.2->==8.3.4==4.1.0->==6.0.0==8.0.1->==8.0.4==0.41.2->==0.45.1==1.32.0->==1.35.1Release Notes
nedbat/coveragepy (coverage)
v7.6.12Compare Source
issue 1927_). These are nowbuilding reliably.
.. _issue 1927:https://github.com/nedbat/coveragepy/issues/19277
.. _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:https://github.com/nedbat/coveragepy/pull/19144
.. _issue 1924https://github.com/nedbat/coveragepy/issues/192424
.. _pytest-dev 67https://github.com/pytest-dev/pytest-cov/issues/676676
.. _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:https://github.com/nedbat/coveragepy/issues/18744
.. _issue 1875https://github.com/nedbat/coveragepy/issues/187575
.. _issue 190https://github.com/nedbat/coveragepy/issues/1902902
.. _issue 19https://github.com/nedbat/coveragepy/issues/19081908
.. _pep649: https://docs.python.org/3.14/whatsnew/3.14.html#pep-649-deferred-evaluation-of-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:https://github.com/nedbat/coveragepy/pull/19011
.. _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:https://github.com/nedbat/coveragepy/issues/18966
.. _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:https://github.com/nedbat/coveragepy/issues/18911
.. _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:https://github.com/pytest-dev/pytest-cov/issues/6666
.. _changes_7-6-4:
v7.6.4Compare Source
withstatements could cause contained branches to beincorrectly marked as missing (
issue 1880_). This is now fixed... _issue 1880:https://github.com/nedbat/coveragepy/issues/18800
.. _changes_7-6-3:
v7.6.3Compare Source
Fix: nested context managers could incorrectly be analyzed to flag a missing
branch on the last context manager, as described in
issue 1876_. This isnow fixed.
Fix: the missing branch message about not exiting a module had an extra
"didn't," as described in
issue 1873_. This is now fixed... _issue 1873:https://github.com/nedbat/coveragepy/issues/18733
.. _issue 1876https://github.com/nedbat/coveragepy/issues/187676
.. _changes_7-6-2:
v7.6.2Compare Source
Dropped support for Python 3.8 and PyPy 3.8.
Fix: a final wildcard match/case clause assigning to a name (
case _ as value) was incorrectly marked as a missing branch. This is now fixed,closing
issue 1860_.Fewer things are considered branches now. Lambdas, comprehensions, and
generator expressions are no longer marked as missing branches if they don't
complete execution. Closes
issue 1852_.Fix: the HTML report didn't properly show multi-line f-strings that end with
a backslash continuation. This is now fixed, closing
issue 1836, thanksto
LiuYinCarl and Marco Ricci <pull 1838_>.Fix: the LCOV report now has correct line numbers (fixing
issue 1846) andbetter branch descriptions for BRDA records (fixing
issue 1850). Thereare other changes to lcov also, including a new configuration option
:ref:
line_checksums <config_lcov_line_checksums>to control whether linechecksums are included in the lcov report. The default is false. To keep
checksums set it to true. All this work is thanks to Zack Weinberg
(
pull 1849_ andpull 1851_).Fixed the docs for multi-line regex exclusions, closing
issue 1863_.Fixed a potential crash in the C tracer, closing
issue 1835, thanks toJan Kühle <pull 1843_>... _issue 1835:https://github.com/nedbat/coveragepy/issues/18355
.. _issue 1836https://github.com/nedbat/coveragepy/issues/183636
.. _pull 183https://github.com/nedbat/coveragepy/pull/1838838
.. _pull 18https://github.com/nedbat/coveragepy/pull/18431843
.. _issue 1https://github.com/nedbat/coveragepy/issues/1846/1846
.. _pull https://github.com/nedbat/coveragepy/pull/1849l/1849
.. _issuehttps://github.com/nedbat/coveragepy/issues/1850es/1850
.. _pulhttps://github.com/nedbat/coveragepy/pull/1851ull/1851
.. _isshttps://github.com/nedbat/coveragepy/issues/1852sues/1852
.. _ishttps://github.com/nedbat/coveragepy/issues/1860ssues/1860
.. _ihttps://github.com/nedbat/coveragepy/issues/1863issues/1863
.. _changes_7-6-1:
v7.6.1Compare Source
Fix: coverage used to fail when measuring code using :func:
runpy.run_path <python:runpy.run_path>with a :class:Path <python:pathlib.Path>argument.This is now fixed, thanks to
Ask Hjorth Larsen <pull 1819_>_.Fix: backslashes preceding a multi-line backslashed string could confuse the
HTML report. This is now fixed, thanks to
LiuYinCarl <pull 1828_>_.Now we publish wheels for Python 3.13, both regular and free-threaded.
.. _pull 1819:https://github.com/nedbat/coveragepy/pull/18199
.. _pull 1828https://github.com/nedbat/coveragepy/pull/182828
.. _changes_7-6-0:
v7.6.0Compare Source
Exclusion patterns can now be multi-line, thanks to
Daniel Diniz <pull 1807_>. This enables many interesting exclusion use-cases, including thoserequested in issues
118 <issue 118_>(entire files),996 <issue 996_>_ (multiple lines only when appearing together),1741 <issue 1741_>_ (remainder of a function), and1803 <issue 1803_>_(arbitrary sequence of marked lines). See the :ref:
multi_line_excludesection of the docs for more details and examples.
The JSON report now includes per-function and per-class coverage information.
Thanks to
Daniel Diniz <pull 1809_>_ for getting the work started. Thiscloses
issue 1793_ andissue 1532_.Fixed an incorrect calculation of "(no class)" lines in the HTML classes
report.
Python 3.13.0b3 is supported.
.. _issue 118:https://github.com/nedbat/coveragepy/issues/1188
.. _issue 996https://github.com/nedbat/coveragepy/issues/99696
.. _issue 153https://github.com/nedbat/coveragepy/issues/1532532
.. _issue 17https://github.com/nedbat/coveragepy/issues/17411741
.. _issue 1https://github.com/nedbat/coveragepy/issues/1793/1793
.. _issue https://github.com/nedbat/coveragepy/issues/1803s/1803
.. _pullhttps://github.com/nedbat/coveragepy/pull/1807ll/1807
.. _pulhttps://github.com/nedbat/coveragepy/pull/1809ull/1809
.. _changes_7-5-4:
v7.5.4Compare Source
If you attempt to combine statement coverage data with branch coverage data,
coverage.py used to fail with the message "Can't combine arc data with line
data" or its reverse, "Can't combine line data with arc data." These
messages used internal terminology, making it hard for people to understand
the problem. They are now changed to mention "branch coverage data" and
"statement coverage data."
Fixed a minor branch coverage problem with wildcard match/case cases using
names or guard clauses.
Started testing on 3.13 free-threading (nogil) builds of Python. I'm not
claiming full support yet. Closes
issue 1799_... _issue 1799:https://github.com/nedbat/coveragepy/issues/17999
.. _changes_7-5-3:
v7.5.3Compare Source
Performance improvements for combining data files, especially when measuring
line coverage. A few different quadratic behaviors were eliminated. In one
extreme case of combining 700+ data files, the time dropped from more than
three hours to seven minutes. Thanks for Kraken Tech for funding the fix.
Performance improvements for generating HTML reports, with a side benefit of
reducing memory use, closing
issue 1791_. Thanks to Daniel Diniz forhelping to diagnose the problem.
.. _issue 1791:https://github.com/nedbat/coveragepy/issues/17911
.. _changes_7-5-2:
v7.5.2Compare Source
Fix: nested matches of exclude patterns could exclude too much code, as
reported in
issue 1779_. This is now fixed.Changed: previously, coverage.py would consider a module docstring to be an
executable statement if it appeared after line 1 in the file, but not
executable if it was the first line. Now module docstrings are never counted
as executable statements. This can change coverage.py's count of the number
of statements in a file, which can slightly change the coverage percentage
reported.
In the HTML report, the filter term and "hide covered" checkbox settings are
remembered between viewings, thanks to
Daniel Diniz <pull 1776_>_.Python 3.13.0b1 is supported.
Fix: parsing error handling is improved to ensure bizarre source files are
handled gracefully, and to unblock oss-fuzz fuzzing, thanks to
Liam DeVoe <pull 1788_>. Closesissue 1787... _pull 1776:https://github.com/nedbat/coveragepy/pull/17766
.. _issue 1779https://github.com/nedbat/coveragepy/issues/177979
.. _issue 178https://github.com/nedbat/coveragepy/issues/1787787
.. _pull 17https://github.com/nedbat/coveragepy/pull/17881788
.. _changes_7-5-1:
v7.5.1Compare Source
Fix: a pragma comment on the continuation lines of a multi-line statement
now excludes the statement and its body, the same as if the pragma is
on the first line. This closes
issue 754. The fix was contributed byDaniel Diniz <pull 1773_>.Fix: very complex source files like
this one <resolvent_lookup_>_ couldcause a maximum recursion error when creating an HTML report. This is now
fixed, closing
issue 1774_.HTML report improvements:
Support files (JavaScript and CSS) referenced by the HTML report now have
hashes added to their names to ensure updated files are used instead of
stale cached copies.
Missing branch coverage explanations that said "the condition was never
false" now read "the condition was always true" because it's easier to
understand.
Column sort order is remembered better as you move between the index pages,
fixing
issue 1766. Thanks,Daniel Diniz <pull 1768_>... _resolvent_lookup: https://github.com/sympy/sympy/blob/130950f3e6b3f97fcc17f4599ac08f70fdd2e9d4/sympy/polys/numberfields/resolvent_lookup.py
.. _issue 754https://github.com/nedbat/coveragepy/issues/75454
.. _issue 176https://github.com/nedbat/coveragepy/issues/1766766
.. _pull 17https://github.com/nedbat/coveragepy/pull/17681768
.. _pull 1https://github.com/nedbat/coveragepy/pull/1773/1773
.. _issue https://github.com/nedbat/coveragepy/issues/1774s/1774
.. _changes_7-5-0:
v7.5.0Compare Source
Added initial support for function and class reporting in the HTML report.
There are now three index pages which link to each other: files, functions,
and classes. Other reports don't yet have this information, but it will be
added in the future where it makes sense. Feedback gladly accepted!
Finishes
issue 780_.Other HTML report improvements:
There is now a "hide covered" checkbox to filter out 100% files, finishing
issue 1384_.The index page is always sorted by one of its columns, with clearer
indications of the sorting.
The "previous file" shortcut key didn't work on the index page, but now it
does, fixing
issue 1765_.The debug output showing which configuration files were tried now shows
absolute paths to help diagnose problems where settings aren't taking effect,
and is renamed from "attempted_config_files" to the more logical
"config_files_attempted."
Python 3.13.0a6 is supported.
.. _issue 780:https://github.com/nedbat/coveragepy/issues/7800
.. _issue 1384https://github.com/nedbat/coveragepy/issues/138484
.. _issue 176https://github.com/nedbat/coveragepy/issues/1765765
.. _changes_7-4-4:
v7.4.4Compare Source
Fix: in some cases, even with
[run] relative_files=True, a data filecould be created with absolute path names. When combined with other relative
data files, it was random whether the absolute file names would be made
relative or not. If they weren't, then a file would be listed twice in
reports, as detailed in
issue 1752_. This is now fixed: absolute filenames are always made relative when combining. Thanks to Bruno Rodrigues dos
Santos for support.
Fix: the last case of a match/case statement had an incorrect message if the
branch was missed. It said the pattern never matched, when actually the
branch is missed if the last case always matched.
Fix: clicking a line number in the HTML report now positions more accurately.
Fix: the
report:formatsetting was defined as a boolean, but should be astring. Thanks,
Tanaydin Sirin <pull 1754_>_. It is also now documentedon the :ref:
configuration page <config_report_format>... _issue 1752:https://github.com/nedbat/coveragepy/issues/17522
.. _pull 1754https://github.com/nedbat/coveragepy/pull/175454
.. _changes_7-4-3:
v7.4.3Compare Source
size during iteration." This is now fixed, closing
issue 1733_... _issue 1733:https://github.com/nedbat/coveragepy/issues/17333
.. _changes_7-4-2:
v7.4.2Compare Source
COVERAGE_CORE=sysmonno longer errors on 3.11 and lower,thanks
Hugo van Kemenade <pull 1747_>_. It now issues a warning thatsys.monitoring is not available and falls back to the default core instead.
.. _pull 1747:https://github.com/nedbat/coveragepy/pull/17477
.. _changes_7-4-1:
v7.4.1Compare Source
Python 3.13.0a3 is supported.
Fix: the JSON report now includes an explicit format version number, closing
issue 1732_... _issue 1732:https://github.com/nedbat/coveragepy/issues/17322
.. _changes_7-4-0:
v7.4.0Compare Source
:mod:
sys.monitoring <python:sys.monitoring>module by defining aCOVERAGE_CORE=sysmonenvironment variable. This should be faster forline coverage, but not for branch coverage, and plugins and dynamic contexts
are not yet supported with it. I am very interested to hear how it works (or
doesn't!) for you.
.. _changes_7-3-4:
v7.3.4Compare Source
Fix: the change for multi-line signature exclusions in 7.3.3 broke other
forms of nested clauses being excluded properly. This is now fixed, closing
issue 1713_.Fix: in the HTML report, selecting code for copying won't select the line
numbers also. Thanks,
Robert Harris <pull 1717_>_... _issue 1713:https://github.com/nedbat/coveragepy/issues/17133
.. _pull 1717https://github.com/nedbat/coveragepy/pull/171717
.. _changes_7-3-3:
v7.3.3Compare Source
Fix: function definitions with multi-line signatures can now be excluded by
matching any of the lines, closing
issue 684. Thanks,Jan Rusak, Maciej Kowalczyk and Joanna Ejzel <pull 1705_>.Fix: XML reports could fail with a TypeError if files had numeric components
that were duplicates except for leading zeroes, like
file1.pyandfile001.py. Fixesissue 1709_.The
coverage annotatecommand used to announce that it would be removedin a future version. Enough people got in touch to say that they use it, so
it will stay. Don't expect it to keep up with other new features though.
Added new :ref:
debug options <cmd_run_debug>:pytestwrites the pytest test name into the debug output.dataop2writes the full data being added to CoverageData objects... _issue 684:https://github.com/nedbat/coveragepy/issues/6844
.. _pull 1705https://github.com/nedbat/coveragepy/pull/170505
.. _issue 170https://github.com/nedbat/coveragepy/issues/1709709
.. _changes_7-3-2:
pycqa/flake8 (flake8)
v7.1.2Compare Source
v7.1.1Compare Source
v7.1.0Compare Source
v7.0.0Compare Source
axw/gocov (github.com/axw/gocov)
v1.2.1Compare Source
What's Changed
New Contributors
Full Changelog: axw/gocov@v1.2.0...v1.2.1
v1.2.0Compare Source
What's Changed
New Contributors
Full Changelog: axw/gocov@v1.1.0...v1.2.0
golangci/golangci-lint (github.com/golangci/golangci-lint)
v1.64.5Compare Source
new-from-merge-base-flagasciicheck: from 0.3.0 to 0.4.0forcetypeassert: from 0.1.0 to 0.2.0gosec: from 2.22.0 to 2.22.1v1.64.4Compare Source
gci: fix standard packages list for go1.24v1.64.3Compare Source
ginkgolinter: from 0.18.4 to 0.19.0go-critic: from 0.11.5 to 0.12.0revive: from 1.6.0 to 1.6.1gci: fix standard packages list for go1.24v1.64.2Compare Source
This is the last minor release of golangci-lint v1.
The next release will be golangci-lint v2.
issues.new-from-merge-baseoptionrun.relative-path-modeoptioncopyloopvar: from 1.1.0 to 1.2.1 (support suggested fixes)exptostd: from 0.3.1 to 0.4.1 (handlesgolang.org/x/exp/constraints.Ordered)fatcontext: from 0.5.3 to 0.7.1 (new option:check-struct-pointers)perfsprint: from 0.7.1 to 0.8.1 (new options:integer-format,error-format,string-format,bool-format, andhex-format)revive: from 1.5.1 to 1.6.0 (new rules:redundant-build-tag,use-errors-new. New optionearly-return.early-return)go-errorlint: from 1.7.0 to 1.7.1gochecknoglobals: from 0.2.1 to 0.2.2godox: from006bad1to 1.1.0gosec: from 2.21.4 to 2.22.0iface: from 1.3.0 to 1.3.1nilnesserr: from 0.1.1 to 0.1.2protogetter: from 0.3.8 to 0.3.9sloglint: from 0.7.2 to 0.9.0spancheck: fix defaultStartSpanMatchersSlicevaluesstaticcheck: from 0.5.1 to 0.6.0tenvis deprecated and replaced byusetesting.os-setenv: true.depguardconfigurationv1.64.1Compare Source
Cancelled due to CI failure.
v1.64.0Compare Source
Cancelled due to CI failure.
v1.63.4Compare Source
dupl,gomodguard,revive: keep only Go-files.v1.63.3Compare Source
v1.63.2Compare Source
v1.63.1Compare Source
golangci-lintis a free and open-source project built by volunteers.If you value it, consider supporting us, the maintainers and linter authors.
We appreciate it! ❤️
For key updates, see the changelog.
Changelog
afa0e27fix: filter files (#5272)ffb15cagci: fix cgo (#5274)v1.63.0Compare Source
v1.62.2Compare Source
fatcontext: from 0.5.2 to 0.5.3ginkgolinter: from 0.18.0 to 0.18.3go-errorlint: from 1.6.0 to 1.7.0iface: from 1.2.0 to 1.2.1revive: from 1.5.0 to 1.5.1testifylint: from 1.5.0 to 1.5.2v1.62.1Compare Source
Cancelled due to CI failure.
v1.62.0Compare Source
recvchecklinter https://github.com/raeperd/recvcheckifacelinter https://github.com/uudashr/ifaceexecinquery: deprecation step 2gomnd: deprecation step 2 (replaced bymnd)bidichk: from 0.2.7 to 0.3.2 (important performance improvement)canonicalheader: from 1.1.1 to 1.1.2cyclop: from 1.2.1 to 1.2.3dupword: from 0.1.1 to 0.1.3errcheck: from 1.7.0 to 1.8.0errchkjson: from 0.3.6 to 0.4.0errname: from 0.1.13 to 1.0.0ginkgolinter: from 0.17.0 to 0.18.0 (new option:force-succeed)go-check-sumtype: from 0.1.4 to 0.2.0 (new option:default-signifies-exhaustive)go-critic: from 0.11.4 to 0.11.5go-printf-func-name: from7558a9eto v0.1.0godot: from 1.4.17 to 1.4.18gosec: from 2.21.2 to 2.21.4intrange: from 0.2.0 to 0.2.1loggercheck: from 0.9.4 to 0.10.1 (log/slogsupport)musttag: from 0.12.2 to 0.13.0nakedret: from 2.0.4 to 2.0.5nilnil: from 0.1.9 to 1.0.0 (new option:detect-opposite)noctx: from 0.0.2 to 0.1.0protogetter: from 0.3.6 to 0.3.8revive: from 1.3.9 to 1.5.0 (new rules:filename-format, andfile-length-limit)tenv: from 1.10.0 to 1.12.1 (handle dot import)testifylint: from 1.4.3 to 1.5.0 (new checkers:contains,encoded-compare,regexp)exclude-dirs-use-defaultforbidigopattern examples for built-in functionsv1.61.0Compare Source
junit-xml-extendedformatdupword: from 0.0.14 to 0.1.1fatcontext: from 0.4.0 to 0.5.2gci: from 0.13.4 to 0.13.5 (new optionno-lex-order)go-ruleguard: from 0.4.2 to0fe6f58(fix panic with custom linters)godot: from 1.4.16 to 1.4.17gomodguard: from 1.3.3 to 1.3.5gosec: disable temporarilyG407gosec: fromab3f6c1to 2.21.2 (partially fixG115)intrange: from 0.1.2 to 0.2.0nolintlint: remove the empty line in the directive replacementtypecheckv1.60.3Compare Source
v1.60.2Compare Source
pytest-dev/pytest (pytest)
v8.3.4Compare Source
pytest 8.3.4 (2024-12-01)
Bug fixes
#12592: Fixed
KeyError{.interpreted-text role="class"} crash when using--import-mode=importlibin a directory layout where a directory contains a child directory with the same name.#12818: Assertion rewriting now preserves the source ranges of the original instructions, making it play well with tools that deal with the
AST, like executing.#12849: ANSI escape codes for colored output now handled correctly in
pytest.fail{.interpreted-text role="func"} with [pytrace=False]{.title-ref}.#9353:
pytest.approx{.interpreted-text role="func"} now uses strict equality when given booleans.Improved documentation
#10558: Fix ambiguous docstring of
pytest.Config.getoption{.interpreted-text role="func"}.#10829: Improve documentation on the current handling of the
--basetempoption and its lack of retention functionality (temporary directory location and retention{.interpreted-text role="ref"}).#12866: Improved cross-references concerning the
recwarn{.interpreted-text role="fixture"} fixture.#12966: Clarify
filterwarnings{.interpreted-text role="ref"} docs on filter precedence/order when using multiple@pytest.mark.filterwarnings <pytest.mark.filterwarnings ref>{.interpreted-text role="ref"} marks.Contributor-facing changes
v8.3.3Compare Source
pytest 8.3.3 (2024-09-09)
Bug fixes
#12446: Avoid calling
@property(and other instance descriptors) during fixture discovery -- byasottile{.interpreted-text role="user"}#12659: Fixed the issue of not displaying assertion failure differences when using the parameter
--import-mode=importlibin pytest>=8.1.#12667: Fixed a regression where type change in [ExceptionInfo.errisinstance]{.title-ref} caused [mypy]{.title-ref} to fail.
#12744: Fixed typing compatibility with Python 3.9 or less -- replaced [typing.Self]{.title-ref} with [typing_extensions.Self]{.title-ref} -- by
Avasam{.interpreted-text role="user"}#12745: Fixed an issue with backslashes being incorrectly converted in nodeid paths on Windows, ensuring consistent path handling across environments.
#6682: Fixed bug where the verbosity levels where not being respected when printing the "msg" part of failed assertion (as in
assert condition, msg).#9422: Fix bug where disabling the terminal plugin via
-p no:terminalwould cause crashes related to missing theverboseoption.-- by
GTowers1{.interpreted-text role="user"}Improved documentation
Miscellaneous internal changes
v8.3.2Compare Source
pytest 8.3.2 (2024-07-24)
Bug fixes
#12652: Resolve regression [conda]{.title-ref} environments where no longer being automatically detected.
-- by
RonnyPfannschmidt{.interpreted-text role="user"}v8.3.1Compare Source
pytest 8.3.1 (2024-07-20)
The 8.3.0 release failed to include the change notes and docs for the release. This patch release remedies this. There are no other changes.
v8.3.0Compare Source
pytest 8.3.0 (2024-07-20)
New features
#12231: Added [--xfail-tb]{.title-ref} flag, which turns on traceback output for XFAIL results.
Some history:
With pytest 8.0, [-rx]{.title-ref} or [-ra]{.title-ref} would not only turn on summary reports for xfail, but also report the tracebacks for xfail results. This caused issues with some projects that utilize xfail, but don't want to see all of the xfail tracebacks.
This change detaches xfail tracebacks from [-rx]{.title-ref}, and now we turn on xfail tracebacks with [--xfail-tb]{.title-ref}. With this, the default [-rx]{.title-ref}/ [-ra]{.title-ref} behavior is identical to pre-8.0 with respect to xfail tracebacks. While this is a behavior change, it brings default behavior back to pre-8.0.0 behavior, which ultimately was considered the better course of action.
#12281: Added support for keyword matching in marker expressions.
Now tests can be selected by marker keyword arguments.
Supported values are
int{.interpreted-text role="class"}, (unescaped)str{.interpreted-text role="class"},bool{.interpreted-text role="class"} &None{.interpreted-text role="data"}.See
marker examples <marker_keyword_expression_example>{.interpreted-text role="ref"} for more information.-- by
lovetheguitar{.interpreted-text role="user"}#12567: Added
--no-fold-skippedcommand line option.If this option is set, then skipped tests in short summary are no longer grouped
by reason but all tests are printed individually with their nodeid in the same
way as other statuses.
-- by
pbrezina{.interpreted-text role="user"}Improvements in existing functionality
#12469: The console output now uses the "third-party plugins" terminology,
replacing the previously established but confusing and outdated
reference to
setuptools <setuptools:index>{.interpreted-text role="std:doc"}-- by
webknjaz{.interpreted-text role="user"}.#12544, #12545: Python virtual environment detection was improved by
checking for a
pyvenv.cfg{.interpreted-text role="file"} file, ensuring reliable detection onvarious platforms -- by
zachsnickers{.interpreted-text role="user"}.#2871: Do not truncate arguments to functions in output when running with [-vvv]{.title-ref}.
#389: The readability of assertion introspection of bound methods has been enhanced
-- by
farbodahm{.interpreted-text role="user"},webknjaz{.interpreted-text role="user"},obestwalter{.interpreted-text role="user"},flub{.interpreted-text role="user"}and
glyphack{.interpreted-text role="user"}.Earlier, it was like:
And now it's like:
#7662: Added timezone information to the testsuite timestamp in the JUnit XML report.
Bug fixes
#11706: Fixed reporting of teardown errors in higher-scoped fixtures when using [--maxfail]{.title-ref} or [--stepwise]{.title-ref}.
Originally added in pytest 8.0.0, but reverted in 8.0.2 due to a regression in pytest-xdist.
This regression was fixed in pytest-xdist 3.6.1.
#11797:
pytest.approx{.interpreted-text role="func"} now correctly handlesSequence <collections.abc.Sequence>{.interpreted-text role="class"}-like objects.#12204, #12264: Fixed a regression in pytest 8.0 where tracebacks get longer and longer when multiple
tests fail due to a shared higher-scope fixture which raised -- by
bluetech{.interpreted-text role="user"}.Also fixed a similar regression in pytest 5.4 for collectors which raise during setup.
The fix necessitated internal changes which may affect some plugins:
FixtureDef.cached_result[2]is now a tuple(exc, tb)instead of
exc.SetupState.stackfailures are now a tuple(exc, tb)instead of
exc.#12275: Fixed collection error upon encountering an
abstract <abc>{.interpreted-text role="mod"} class, including abstract [unittest.TestCase]{.title-ref} subclasses.#12328: Fixed a regression in pytest 8.0.0 where package-scoped parameterized items were not correctly reordered to minimize setups/teardowns in some cases.
[#12424](https://redirect.github.com/pyte
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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.