fix(deps): update python dependencies (major) #363
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
2 times, most recently
from
3113950 to
1cc7029
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
from
1cc7029 to
4282876
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
2 times, most recently
from
658da7d to
3df7336
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
6 times, most recently
from
7ddd0a8 to
3ae7a48
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
6 times, most recently
from
f9a8b70 to
1d1ebfa
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
2 times, most recently
from
80bc923 to
08780fb
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
from
08780fb to
e795612
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
2 times, most recently
from
9ed00ef to
d2c7c09
Compare
renovate
bot
changed the title
|
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
2 times, most recently
from
8851878 to
37bbbe0
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
2 times, most recently
from
d081e2e to
268294e
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
from
268294e to
98fac6f
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
from
98fac6f to
67ca508
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
3 times, most recently
from
3a6f56f to
78d76cc
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
2 times, most recently
from
9fec02f to
d22a29f
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
2 times, most recently
from
f8c986c to
2991c9d
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
2 times, most recently
from
2b10f9c to
abe34d9
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
from
abe34d9 to
bb58c5f
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
6 times, most recently
from
1a6326e to
478664a
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
4 times, most recently
from
4f89532 to
d3350bf
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
from
d3350bf to
7e4f749
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
from
7e4f749 to
a8b7634
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:
^24.4.2->^25.0.0^2.5.0->^3.0.0^5.13.2->^6.0.0^30.1.0->^33.0.02.21.1->3.2.0^0.21.1->^1.0.0Release Notes
psf/black (black)
v25.1.0Compare Source
Highlights
This release introduces the new 2025 stable style (#4558), stabilizing the following
changes:
# fmt: skipcomments is no longer normalized (#4146)(#4154)
*and more complex type variable tuple (#4440)The following changes were not in any previous release:
over multiple lines first instead of type parameter definitions (#4553)
Stable style
empty lines (#4484)
withstatements containing tuple generators/unpacking(#4538)
Preview style
(#4498)
string_processingandwrap_long_dict_values_in_parensfrom removingparentheses around long dictionary values (#4377)
wrap_long_dict_values_in_parensfrom the unstable to preview style (#4561)Packaging
License-Expressionmetadata field, seePEP 639. (#4479)
Performance
is_fstring_startfunction in Black's tokenizer (#4541)Integrations
--stdin-filenameset to a force excluded path, stdin won't beformatted. (#4539)
gforcada/flake8-builtins (flake8-builtins)
v3.0.0Compare Source
Change
A005to report errors on first line, rather than on line zero.[tremblaysimon]
Add support for Python 3.13.
[gforcada]
PyCQA/isort (isort)
v6.0.1Compare Source
Changes
🪲 Fixes
👷 Continuous Integration
v6.0.0Compare Source
Changes
💥 Breaking Changes
🚀 Features
asimports (#2340) @DanielNoordpre-commit autoupdate(#2321) @kurtmckee🪲 Fixes
--diffto be used with--jobs(#2302) @mnakamawemakehas 80 chars hard limit, not 79 (#2241) @sobolevnmain(#2320) @DanielNoordsort_reexportscode mangling (#2283) @Helveg👷 Continuous Integration
actions/cache@v2usage (#2322) @kurtmckeepre-commit(#2296) @matthewhughes934📦 Dependencies
poetryto2.0.1(#2341) @DanielNoordkubernetes-client/python (kubernetes)
v33.1.0: Kubernetes Python Client v33.1.0 Stable ReleaseCompare Source
Getting started:
Or from source, download attached zip file, then
unzip client-python-v33.1.0.zip cd client-python-v33.1.0 python setup.py installThen follow examples in https://github.com/kubernetes-client/python/tree/release-33.0/examples
Changelog: https://github.com/kubernetes-client/python/blob/release-33.0/CHANGELOG.md
v32.0.1Compare Source
Kubernetes API Version: v1.32.2
Uncategorized
Bug or Regression
Feature
applyparameter for functions within theutils.create_from_yamlsubmodule. This allows these functions to optionally use theDynamicClient.server_side_applyfunction to apply yaml manifests. (#2252, @dcmcand)utils.format_quantityto convert decimal numbers into a canonical Kubernetes quantity. (#2216, @rkschamer)v32.0.0Compare Source
Kubernetes API Version: v1.32.1
Bug or Regression
v31.0.0Compare Source
Kubernetes API Version: v1.31.0
canonical/operator (ops)
v3.2.0Compare Source
Features
Documentation
Layerinstead of aLayerDictin the httpbin charm (#2003)CI
v3.1.0Compare Source
Features
Fixes
Documentation
opsversion in Charmcraft profiles (#1872)Tests
CI
v3.0.0Compare Source
The minimum version of Python for Ops 3.x is 3.10.
Documentation
CI
v2.23.1: : Add the remote unit to Relation.data, but not Relation.unitsCompare Source
This is a small bug-fix release for the 2.x series that addresses issues with the recent feature making relation data available in relation-departed events. Rather than inserting the remote unit into
Relation.units, the data is available fromRelation.data, without changingRelation.units.What's Changed
Fixes
Relation.databut notRelation.unitsin #1928Documentation
self.appandself.unitin #1856CI
Full Changelog: canonical/operator@2.23.0...2.23.1
v2.23.0Compare Source
Features
Fixes
Documentation
CI
v2.22.0Compare Source
Features
Fixes
__init__(#1737)ops.testing(#1754)Documentation
CI
ops[tracing]integration tests (#1686)alertmanager-k8s-operatorin observability charm tests (#1753)ops[tracing]addition (#1755)pytest-dev/pytest-asyncio (pytest-asyncio)
v1.1.0: pytest-asyncio 1.1.0Compare Source
Added
loop_scopeends (#200)Fixed
finallyclause of a task (#878)Notes for Downstream Packagers
v1.0.0: pytest-asyncio 1.0.0Compare Source
1.0.0 - 2025-05-26
Removed
(#1106)
Added
(#1025)
Changed
than per scope (e.g. per module). This reduces the number of fixtures
and speeds up collection time, especially for large test suites.
(#1107)
pytest.mark.asynciono longer forcesthat a pytest Collector exists at the level of the specified scope.
For example, a test function marked with
pytest.mark.asyncio(loop_scope="class")no longer requires a classsurrounding the test. This is consistent with the behavior of the
scope argument to
pytest_asyncio.fixture.(#1112)
Fixed
option.
(#630)
--doctest-ignore-import-errors(#797)
(#1052)
Notes for Downstream Packagers
(#1114)
v0.26.0: pytest-asyncio 0.26.0Compare Source
pytest_asyncio.fixture#1045typing-extensionsas additional dependency for Python<3.10#1045v0.25.3: pytest-asyncio 0.25.3Compare Source
v0.25.2: pytest-asyncio 0.25.2Compare Source
loop.shutdown_asyncgens()before closing the event loop to ensure async generators are closed in the same manner asasyncio.rundoes #1034v0.25.1: pytest-asyncio 0.25.1Compare Source
v0.25.0: pytest-asyncio 0.25.0Compare Source
0.25.0 (2024-12-13)
@pytest.fixturein strict mode. This will become an error in a future version of flake8-asyncio. #979v0.24.0: pytest-asyncio 0.24.0Compare Source
0.24.0 (2024-08-22)
pytest_asyncio.fixture. Users are encouraged to use the loop_scope keyword argument, which does exactly the same.@pytest.mark.asyncio. #812v0.23.8: pytest-asyncio 0.23.8Compare Source
0.23.8 (2024-07-17)
Known issues
As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.
v0.23.7: pytest-asyncio 0.23.7Compare Source
0.23.7 (2024-05-19)
Known issues
As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.
v0.23.6: pytest-asyncio 0.23.6Compare Source
0.23.6 (2024-03-19)
Known issues
As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.
v0.23.5: pytest-asyncio 0.23.5Compare Source
0.23.5 (2024-02-09)
asyncio.get_event_loop()from affecting test cases #757Known issues
As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.
v0.23.4: pytest-asyncio 0.23.4Compare Source
0.23.4 (2024-01-28)
v0.23.3: pytest-asyncio 0.23.3Compare Source
0.23.3 (2024-01-01)
Known issues
As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.
v0.23.2: pytest-asyncio 0.23.2Compare Source
0.23.2 (2023-12-04)
v0.23.1: pytest-asyncio 0.23.1Compare Source
0.23.1 (2023-12-03)
v0.23.0: pytest-asyncio 0.23.0Compare Source
This release is backwards-compatible with v0.21. Changes are
non-breaking, unless you upgrade from v0.22.
loops with class, module, package, and session scopes can be
requested via the scope keyword argument to the asyncio
mark.
non-default or multiple event loops #662
pytest_asyncio.is_async_testwhich returns whether atest item is managed by pytest-asyncio #376
dependencies #620, #674, #678
v0.22.0: pytest-asyncio 0.22.0 (yanked)Compare Source
This release deprecated event loop overrides, but didn't provide adequate replacement functionality for all relevant use cases. As such, the release was yanked from PyPI.
0.22.0 (2023-10-31)
via the asyncio_event_loop mark. #620
Users requiring a class-scoped or module-scoped asyncio event loop for their tests
should mark the corresponding class or module with asyncio_event_loop.
Configuration
📅 Schedule: Branch creation - "after 1am and before 2am 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 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.