Update Python dependencies (major) #124
Merged
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
requested review from
a team,
paulomach,
taurus-forever,
shayancanonical and
carlcsaposs-canonical
and removed request for
a team
taurus-forever
approved these changes
Apr 10, 2024
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
from
baa1b4b
to
9ffde59
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
from
9ffde59
to
3886f4f
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
from
3886f4f
to
96791a8
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
from
96791a8
to
1e93d69
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
from
1e93d69
to
04e9c72
Compare
|
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
2 times, most recently
from
ad85ffa
to
fdc6a1b
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
from
0ba2fcb
to
0fc1a9a
Compare
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. |
carlcsaposs-canonical
approved these changes
Jul 8, 2024
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:
^23.12.1->^24.4.2^6.1.0->^7.1.0^5.8.1->^6.1.1^6.1.0->^7.0.0^7.4.4->^8.2.2^4.1.0->^5.0.0Release Notes
psf/black (black)
v24.4.2Compare Source
This is a bugfix release to fix two regressions in the new f-string parser introduced in
24.4.1.
Parser
Performance
v24.4.1Compare Source
Highlights
Stable style
Parser
by PEP 696 (#4327)
Integrations
git archiveis skipped (#4313)v24.4.0Compare Source
Stable style
Preview style
ifguards incaseblocks are now wrapped in parentheses when the line is too long.(#4269)
Integrations
use_pyprojectto the GitHub Actionpsf/black. This will read theBlack version from
pyproject.toml. (#4294)v24.3.0Compare Source
Highlights
This release is a milestone: it fixes Black's first CVE security vulnerability. If you
run Black on untrusted input, or if you habitually put thousands of leading tab
characters in your docstrings, you are strongly encouraged to upgrade immediately to fix
CVE-2024-21503.
This release also fixes a bug in Black's AST safety check that allowed Black to make
incorrect changes to certain f-strings that are valid in Python 3.12 and higher.
Stable style
of Black would incorrectly format the contents of certain unusual f-strings containing
nested strings with the same quote type. Now, Black will crash on such strings until
support for the new f-string syntax is implemented. (#4270)
(#4273)
Performance
characters. This fixes
CVE-2024-21503.
(#4278)
Documentation
--checkis used with--quiet(#4236)v24.2.0Compare Source
Stable style
(#4218)
Preview style
hug_parens_with_braces_and_square_bracketsfeature to the unstable styledue to an outstanding crash and proposed formatting tweaks (#4198)
expression (#4154)
(#4185)
casestatementifguards (#4214).Configuration
pyproject.tomlthat is missing atool.blacksection whendiscovering project root and configuration. Since Black continues to use version
control as an indicator of project root, this is expected to primarily change behavior
for users in a monorepo setup (desirably). If you wish to preserve previous behavior,
simply add an empty
[tool.black]to the previously discoveredpyproject.toml(#4204)
Output
SyntaxWarnings orDeprecationWarnings produced by theastmodule when performing equivalence checks (#4189)
Integrations
v24.1.1Compare Source
Bugfix release to fix a bug that made Black unusable on certain file systems with strict
limits on path length.
Preview style
Configuration
do not support long paths (#4176)
v24.1.0Compare Source
Highlights
This release introduces the new 2024 stable style (#4106), stabilizing the following
changes:
if-elseexpressions (#2278)...are formatted morecompactly (#3796)
(#3368)
withstatement(#3489)
entry (#3393)
--skip-magic-trailing-commaor-C, trailing commas are stripped fromsubscript expressions with more than 1 element (#3209)
# fmt: skipwith other comments (#3959)There are already a few improvements in the
--previewstyle, which are slated for the2025 stable style. Try them out and
share your feedback. In the past, the preview
style has included some features that we were not able to stabilize. This year, we're
adding a separate
--unstablestyle for features with known problems. Now, the--previewstyle only includes features that we actually expect to make it into nextyear's stable style.
Stable style
Several bug fixes were made in features that are moved to the stable style in this
release:
unlike other binary operators (#4109)
blocks, except immediately before a docstring (#4130)
Preview style
--unstablestyle, covering preview features that have known problems that wouldblock them from going into the stable style. Also add the
--enable-unstable-featureflag; for example, use
--enable-unstable-feature hug_parens_with_braces_and_square_bracketsto apply thispreview feature throughout 2024, even if a later Black release downgrades the feature
to unstable (#4096)
# fmt: skipcomments (#4146)Configuration
pyproject.tomlcontains an invalid key (#4165)--experimental-string-processingflag. This feature cancurrently be enabled with
--preview --enable-unstable-feature string_processing.(#4096)
Integrations
(#3940) for better compatibility with older versions of pre-commit (#4137)
pycqa/flake8 (flake8)
v7.1.0Compare Source
v7.0.0Compare Source
canonical/ops-scenario (ops-scenario)
v6.1.1Compare Source
v6.1.0Compare Source
v6.0.5Compare Source
v6.0.4Compare Source
v6.0.3Compare Source
v6.0.2Compare Source
v6.0.1Compare Source
v6.0Compare Source
csachs/pyproject-flake8 (pyproject-flake8)
v7.0.0Compare Source
pytest-dev/pytest (pytest)
v8.2.2Compare Source
pytest 8.2.2 (2024-06-04)
Bug Fixes
.pytest_cache) creation. Regressed in pytest 8.2.0.Improved Documentation
lack of thread safety in pytest as a possible source of flakyness.
v8.2.1Compare Source
pytest 8.2.1 (2024-05-19)
Improvements
Bug Fixes
.pytest_cachedirectories becamerwx------instead of the expectedrwxr-xr-x.Trivial/Internal Changes
v8.2.0Compare Source
pytest 8.2.0 (2024-04-27)
Deprecations
#12069: A deprecation warning is now raised when implementations of one of the following hooks request a deprecated
py.path.localparameter instead of thepathlib.Pathparameter which replaced it:pytest_ignore_collect{.interpreted-text role="hook"} - thepathparameter - usecollection_pathinstead.pytest_collect_file{.interpreted-text role="hook"} - thepathparameter - usefile_pathinstead.pytest_pycollect_makemodule{.interpreted-text role="hook"} - thepathparameter - usemodule_pathinstead.pytest_report_header{.interpreted-text role="hook"} - thestartdirparameter - usestart_pathinstead.pytest_report_collectionfinish{.interpreted-text role="hook"} - thestartdirparameter - usestart_pathinstead.The replacement parameters are available since pytest 7.0.0.
The old parameters will be removed in pytest 9.0.0.
See
legacy-path-hooks-deprecated{.interpreted-text role="ref"} for more details.Features
#11871: Added support for reading command line arguments from a file using the prefix character
@, like e.g.:pytest @​tests.txt. The file must have one argument per line.See
Read arguments from file <args-from-file>{.interpreted-text role="ref"} for details.Improvements
#11523:
pytest.importorskip{.interpreted-text role="func"} will now issue a warning if the module could be found, but raisedImportError{.interpreted-text role="class"} instead ofModuleNotFoundError{.interpreted-text role="class"}.The warning can be suppressed by passing
exc_type=ImportErrortopytest.importorskip{.interpreted-text role="func"}.See
import-or-skip-import-error{.interpreted-text role="ref"} for details.#11728: For
unittest-based tests, exceptions during class cleanup (as raised by functions registered withTestCase.addClassCleanup <unittest.TestCase.addClassCleanup>{.interpreted-text role="meth"}) are now reported instead of silently failing.#11777: Text is no longer truncated in the
short test summary infosection when-vvis given.#12112: Improved namespace packages detection when
consider_namespace_packages{.interpreted-text role="confval"} is enabled, covering more situations (like editable installs).#9502: Added
PYTEST_VERSION{.interpreted-text role="envvar"} environment variable which is defined at the start of the pytest session and undefined afterwards. It contains the value ofpytest.__version__, and among other things can be used to easily check if code is running from within a pytest run.Bug Fixes
#12065: Fixed a regression in pytest 8.0.0 where test classes containing
setup_methodand tests using@staticmethodor@classmethodwould crash withAttributeError: 'NoneType' object has no attribute 'setup_method'.Now the
request.instance <pytest.FixtureRequest.instance>{.interpreted-text role="attr"} attribute of tests using@staticmethodand@classmethodis no longerNone, but a fresh instance of the class, like in non-static methods.Previously it was
None, and all fixtures of such tests would share a singleself.#12135: Fixed issue where fixtures adding their finalizer multiple times to fixtures they request would cause unreliable and non-intuitive teardown ordering in some instances.
#12194: Fixed a bug with
--importmode=importliband--doctest-moduleswhere child modules did not appear as attributes in parent modules.#1489: Fixed some instances where teardown of higher-scoped fixtures was not happening in the reverse order they were initialized in.
Trivial/Internal Changes
pluggy>=1.5.0is now required.cache <cache>{.interpreted-text role="ref"}: create supporting files (CACHEDIR.TAG,.gitignore, etc.) in a temporary directory to provide atomic semantics.v8.1.2Compare Source
pytest 8.1.2 (2024-04-26)
Bug Fixes
pytest.approx{.interpreted-text role="func"} when used with [numpy]{.title-ref} arrays and comparing with other types.v8.1.1Compare Source
pytest 8.1.1 (2024-03-08)
::: {.note}
::: {.title}
Note
:::
This release is not a usual bug fix release -- it contains features and improvements, being a follow up
to
8.1.0, which has been yanked from PyPI.:::
Features
#11475: Added the new
consider_namespace_packages{.interpreted-text role="confval"} configuration option, defaulting toFalse.If set to
True, pytest will attempt to identify modules that are part of namespace packages when importing modules.#11653: Added the new
verbosity_test_cases{.interpreted-text role="confval"} configuration option for fine-grained control of test execution verbosity.See
Fine-grained verbosity <pytest.fine_grained_verbosity>{.interpreted-text role="ref"} for more details.Improvements
#10865:
pytest.warns{.interpreted-text role="func"} now validates thatwarnings.warn{.interpreted-text role="func"} was called with a [str]{.title-ref} or a [Warning]{.title-ref}.Currently in Python it is possible to use other types, however this causes an exception when
warnings.filterwarnings{.interpreted-text role="func"} is used to filter those warnings (see CPython #103577 for a discussion).While this can be considered a bug in CPython, we decided to put guards in pytest as the error message produced without this check in place is confusing.
#11311: When using
--override-inifor paths in invocations without a configuration file defined, the current working directory is usedas the relative directory.
Previoulsy this would raise an
AssertionError{.interpreted-text role="class"}.#11475:
--import-mode=importlib <import-mode-importlib>{.interpreted-text role="ref"} now tries to import modules using the standard import mechanism (but still without changing :pysys.path{.interpreted-text role="data"}), falling back to importing modules directly only if that fails.This means that installed packages will be imported under their canonical name if possible first, for example
app.core.models, instead of having the module name always be derived from their path (for example.env310.lib.site_packages.app.core.models).#11801: Added the
iter_parents() <_pytest.nodes.Node.iter_parents>{.interpreted-text role="func"} helper method on nodes.It is similar to
listchain <_pytest.nodes.Node.listchain>{.interpreted-text role="func"}, but goes from bottom to top, and returns an iterator, not a list.#11850: Added support for
sys.last_exc{.interpreted-text role="data"} for post-mortem debugging on Python>=3.12.#11962: In case no other suitable candidates for configuration file are found, a
pyproject.toml(even without a[tool.pytest.ini_options]table) will be considered as the configuration file and define therootdir.#11978: Add
--log-file-modeoption to the logging plugin, enabling appending to log-files. This option accepts either"w"or"a"and defaults to"w".Previously, the mode was hard-coded to be
"w"which truncates the file before logging.#12047: When multiple finalizers of a fixture raise an exception, now all exceptions are reported as an exception group.
Previously, only the first exception was reported.
Bug Fixes
#11475: Fixed regression where
--importmode=importlibwould import non-test modules more than once.#11904: Fixed a regression in pytest 8.0.0 that would cause test collection to fail due to permission errors when using
--pyargs.This change improves the collection tree for tests specified using
--pyargs, see12043{.interpreted-text role="pull"} for a comparison with pytest 8.0 and <8.#12011: Fixed a regression in 8.0.1 whereby
setup_modulexunit-style fixtures are not executed when--doctest-modulesis passed.#12014: Fix the
stacklevelused when warning about marks used on fixtures.#12039: Fixed a regression in
8.0.2where tests created usingtmp_path{.interpreted-text role="fixture"} have been collected multiple times in CI under Windows.Improved Documentation
tmp_pathfixture in more detail.Trivial/Internal Changes
#11785: Some changes were made to private functions which may affect plugins which access them:
FixtureManager._getautousenames()now takes aNodeitself instead of the nodeid.FixtureManager.getfixturedefs()now takes theNodeitself instead of the nodeid._pytest.nodes.iterparentnodeids()function is removed without replacement.Prefer to traverse the node hierarchy itself instead.
If you really need to, copy the function from the previous pytest release.
#12069: Delayed the deprecation of the following features to
9.0.0:node-ctor-fspath-deprecation{.interpreted-text role="ref"}.legacy-path-hooks-deprecated{.interpreted-text role="ref"}.It was discovered after
8.1.0was released that the warnings about the impeding removal were not being displayed, so the team decided to revert the removal.This is the reason for
8.1.0being yanked.pytest 8.1.0 (YANKED)
::: {.note}
::: {.title}
Note
:::
This release has been yanked: it broke some plugins without the proper warning period, due to
some warnings not showing up as expected.
See #12069.
:::
v8.1.0Compare Source
pytest 8.1.0 (YANKED)
Features
#11475: Added the new
consider_namespace_packages{.interpreted-text role="confval"} configuration option, defaulting toFalse.If set to
True, pytest will attempt to identify modules that are part of namespace packages when importing modules.#11653: Added the new
verbosity_test_cases{.interpreted-text role="confval"} configuration option for fine-grained control of test execution verbosity.See
Fine-grained verbosity <pytest.fine_grained_verbosity>{.interpreted-text role="ref"} for more details.Improvements
#10865:
pytest.warns{.interpreted-text role="func"} now validates thatwarnings.warn{.interpreted-text role="func"} was called with a [str]{.title-ref} or a [Warning]{.title-ref}.Currently in Python it is possible to use other types, however this causes an exception when
warnings.filterwarnings{.interpreted-text role="func"} is used to filter those warnings (see CPython #103577 for a discussion).While this can be considered a bug in CPython, we decided to put guards in pytest as the error message produced without this check in place is confusing.
#11311: When using
--override-inifor paths in invocations without a configuration file defined, the current working directory is usedas the relative directory.
Previoulsy this would raise an
AssertionError{.interpreted-text role="class"}.#11475:
--import-mode=importlib <import-mode-importlib>{.interpreted-text role="ref"} now tries to import modules using the standard import mechanism (but still without changing :pysys.path{.interpreted-text role="data"}), falling back to importing modules directly only if that fails.This means that installed packages will be imported under their canonical name if possible first, for example
app.core.models, instead of having the module name always be derived from their path (for example.env310.lib.site_packages.app.core.models).#11801: Added the
iter_parents() <_pytest.nodes.Node.iter_parents>{.interpreted-text role="func"} helper method on nodes.It is similar to
listchain <_pytest.nodes.Node.listchain>{.interpreted-text role="func"}, but goes from bottom to top, and returns an iterator, not a list.#11850: Added support for
sys.last_exc{.interpreted-text role="data"} for post-mortem debugging on Python>=3.12.#11962: In case no other suitable candidates for configuration file are found, a
pyproject.toml(even without a[tool.pytest.ini_options]table) will be considered as the configuration file and define therootdir.#11978: Add
--log-file-modeoption to the logging plugin, enabling appending to log-files. This option accepts either"w"or"a"and defaults to"w".Previously, the mode was hard-coded to be
"w"which truncates the file before logging.#12047: When multiple finalizers of a fixture raise an exception, now all exceptions are reported as an exception group.
Previously, only the first exception was reported.
Bug Fixes
#11904: Fixed a regression in pytest 8.0.0 that would cause test collection to fail due to permission errors when using
--pyargs.This change improves the collection tree for tests specified using
--pyargs, see12043{.interpreted-text role="pull"} for a comparison with pytest 8.0 and <8.#12011: Fixed a regression in 8.0.1 whereby
setup_modulexunit-style fixtures are not executed when--doctest-modulesis passed.#12014: Fix the
stacklevelused when warning about marks used on fixtures.#12039: Fixed a regression in
8.0.2where tests created usingtmp_path{.interpreted-text role="fixture"} have been collected multiple times in CI under Windows.Improved Documentation
tmp_pathfixture in more detail.Trivial/Internal Changes
FixtureManager._getautousenames()now takes aNodeitself instead of the nodeid.FixtureManager.getfixturedefs()now takes theNodeitself instead of the nodeid._pytest.nodes.iterparentnodeids()function is removed without replacement.Prefer to traverse the node hierarchy itself instead.
If you really need to, copy the function from the previous pytest release.
v8.0.2Compare Source
pytest 8.0.2 (2024-02-24)
Bug Fixes
c:\PROGRA~1\tests).IndexErrorcrash raising fromgetstatementrange_ast.v8.0.1Compare Source
pytest 8.0.1 (2024-02-16)
Bug Fixes
getpass.getuser{.interpreted-text role="func"} in Python 3.13.ExceptionInfo._stringify_exceptioncould crashpytest.raises{.interpreted-text role="func"}.pytest.warns{.interpreted-text role="func"} using custom warning subclasses which have more than one parameter in their [__init__]{.title-ref}.pytest.skip{.interpreted-text role="func"} and similar control-flow exceptions within apytest.warns(){.interpreted-text role="func"} block would get suppressed instead of propagating.v8.0.0: pytest 8.0.0 (2024-01-27)Compare Source
See 8.0.0rc1 and 8.0.0rc2 for the full changes since pytest 7.4!
Bug Fixes
reasonof askip <pytest.mark.skip ref>{.interpreted-text role="ref"} mark when writing JUnit XML files.1_000_000when usinglog-date-formatwith%fspecifier, which might cause the test suite to crash.pytest-dev/pytest-cov (pytest-cov)
v5.0.0Compare Source
Contributed by Matthias Reichenbach in
#​623 <https://github.com/pytest-dev/pytest-cov/pull/623>_.Contributed by Christian Clauss and Hugo van Kemenade in
#​630 <https://github.com/pytest-dev/pytest-cov/pull/630>,#​631 <https://github.com/pytest-dev/pytest-cov/pull/631>,#​632 <https://github.com/pytest-dev/pytest-cov/pull/632>_ and#​633 <https://github.com/pytest-dev/pytest-cov/pull/633>_.pyproject.tomlexample in the docs.Contributed by Dawn James in
#​626 <https://github.com/pytest-dev/pytest-cov/pull/626>_.Christian Clauss in
#​584 <https://github.com/pytest-dev/pytest-cov/pull/584>_.Configuration
📅 Schedule: Branch creation - "after 1am and before 3am every weekday" in timezone Etc/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 has been generated by Mend Renovate. View repository job log here.