Update Python dependencies (major) #69
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
force-pushed
the
renovate/major-python-dependencies
branch
5 times, most recently
from
0a11057 to
9a25cf0
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
4 times, most recently
from
d698963 to
0301b25
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
5 times, most recently
from
ec2a940 to
8016e16
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
from
8016e16 to
d3378f5
Compare
renovate
bot
force-pushed
the
renovate/major-python-dependencies
branch
from
d3378f5 to
3115007
Compare
deusebio
approved these changes
Mar 27, 2024
welpaolo
approved these changes
Mar 27, 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:
==3.7.1->==4.3.0==2023.11.17->==2024.2.25.0.4->7.0.0==0.18.0->==1.0.423.3.0->24.1.07.4.4->8.1.14.1.0->5.0.0Release Notes
agronholm/anyio (anyio)
v4.3.0Compare Source
Added support for the Python 3.12
walk_upkeyword argument inanyio.Path.relative_to()(PR by Colin Taylor)Fixed passing
total_tokenstoanyio.CapacityLimiter()as a keyword argument not working on thetriobackend (#515)Fixed
Process.aclose()not performing the minimum level of necessary cleanup when cancelled. Previously:Process.aclose()could leak an orphan processrun_process()could very briefly leak an orphan process.Process.aclose()orrun_process()on Trio could leave standard streams unclosed(PR by Ganden Schaffner)
Fixed
Process.stdin.aclose(),Process.stdout.aclose(), andProcess.stderr.aclose()not including a checkpoint on asyncio (PR by Ganden Schaffner)Fixed documentation on how to provide your own typed attributes
v4.2.0Compare Source
Add support for
byte-based paths inconnect_unix,create_unix_listeners,create_unix_datagram_socket, andcreate_connected_unix_datagram_socket. (PR by Lura Skye)Enabled the
EventandCapacityLimiterclasses to be instantiated outside an event loop threadBroadly improved/fixed the type annotations. Among other things, many functions and methods that take variadic positional arguments now make use of PEP 646
TypeVarTupleto allow the positional arguments to be validated by static type checkers. These changes affected numerous methods and functions, including:anyio.run()TaskGroup.start_soon()anyio.from_thread.run()anyio.from_thread.run_sync()anyio.to_thread.run_sync()anyio.to_process.run_sync()BlockingPortal.call()BlockingPortal.start_task_soon()BlockingPortal.start_task()(also resolves #560)
Fixed various type annotations of
anyio.Pathto match Typeshed:anyio.Path.__lt__()anyio.Path.__le__()anyio.Path.__gt__()anyio.Path.__ge__()anyio.Path.__truediv__()anyio.Path.__rtruediv__()anyio.Path.hardlink_to()anyio.Path.samefile()anyio.Path.symlink_to()anyio.Path.with_segments()(PR by Ganden Schaffner)
Fixed adjusting the total number of tokens in a
CapacityLimiteron asyncio failing to wake up tasks waiting to acquire the limiter in certain edge cases (fixed with help from Egor Blagov)Fixed
loop_factoryanduse_uvloopoptions not being used on the asyncio backend (#643)Fixed cancellation propagating on asyncio from a task group to child tasks if the task hosting the task group is in a shielded cancel scope (#642)
v4.1.0Compare Source
trio.to_thread.run_sync()using theabandon_on_cancelkeyword argument instead ofcancellablecancellableargument inanyio.to_thread.run_sync()toabandon_on_cancel(and deprecated the old parameter name)anyio.from_thread.check_cancelled()ResourceGuardclass in the public API (#627)RuntimeError: Runner is closedwhen running higher-scoped async generator fixtures in some cases (#619)asyncioandtriowhere reraising a cancellation exception in anexcept*block would incorrectly bubble out of its cancel scope (#634)v4.0.0Compare Source
ExceptionGroupclass with the PEP 654BaseExceptionGroupandExceptionGroupExceptionGroup(orBaseExceptionGroupif one or moreBaseExceptionwere included)TaskGroupalways hits a yield point, regardless of whether there are running child tasks to be waited onanyio.Path.relative_to()andanyio.Path.is_relative_to()to only accept one argument, as passing multiple arguments is deprecated as of Python 3.12@asyncio.coroutine)policyoption on theasynciobackend was changed toloop_factoryto accommodateasyncio.Runneranyio.run()to useasyncio.Runner(or a back-ported version of it on Pythons older than 3.11) on theasynciobackendanyio.Path.is_junction()andanyio.Path.walk()methodscreate_unix_datagram_socketandcreate_connected_unix_datagram_socketto create UNIX datagram sockets (PR by Jean Hominal)from_thread.runandfrom_thread.run_syncnot setting sniffio on asyncio. As a result:from_thread.run_syncfailing when used to call sniffio-dependent functions on asynciofrom_thread.runfailing when used to call sniffio-dependent functions on asyncio from a thread running trio or curiofrom_thread.start_blocking_portal(backend="asyncio")in a thread running trio or curio (PR by Ganden Schaffner)item_typeargument ofcreate_memory_object_streamwas deprecated. To indicate the item type handled by the stream, usecreate_memory_object_stream[T_Item]()instead. Type checking should no longer fail when annotating memory object streams with uninstantiable item types (PR by Ganden Schaffner)CancelScope.cancelled_caughtproperty which tells users if the cancel scope suppressed a cancellation exceptionfail_after()raising an unwarrantedTimeoutErrorwhen the cancel scope was cancelled before reaching its deadlineMemoryObjectReceiveStream.receive()causing the receiving task on asyncio to remain in a cancelled state if the operation was cancelled after an item was queued to be received by the task (but before the task could actually receive the item)TaskGroup.start()on asyncio not responding to cancellation from the outsideBlockingPortalnot notifying synchronous listeners (concurrent.futures.wait()) when they're cancelledEvent.wait()on asyncio in the case where the event was not yet setanyio.to_process()being "lost" as unusable to the process pool when processes that have idled over 5 minutes are pruned at part of theto_process.run_sync()call, leading to increased memory consumption (PR by Anael Gorfinkel)Changes since 4.0.0rc1:
TaskGroup.start_soon()to accept any awaitables (already in v3.7.0 but was missing from 4.0.0rc1)CancelScopeto also consider the cancellation count (in addition to the cancel message) on asyncio to determine if a cancellation exception should be swallowed on scope exit, to combat issues where third party libraries catch theCancelledErrorand raise another, thus erasing the original cancel messageTLSListener.handle_handshake_error()on asyncio to log"NoneType: None"instead of the error (PR by Ganden Schaffner)item_typeargument tocreate_memory_object_stream()(but using it raises a deprecation warning and does nothing with regards to the static types of the returned streams)anyio.to_process()being "lost" as unusable to the process pool when processes that have idled over 5 minutes are pruned at part of theto_process.run_sync()call, leading to increased memory consumption (PR by Anael Gorfinkel)certifi/python-certifi (certifi)
v2024.2.2Compare Source
pycqa/flake8 (flake8)
v7.0.0Compare Source
v6.1.0Compare Source
v6.0.0Compare Source
encode/httpcore (httpcore)
v1.0.4Compare Source
targetrequest extension. (#888)UpgradeandCONNECTwhen some data in the stream has been read. (#882)v1.0.3Compare Source
v1.0.2Compare Source
float("inf")timeouts inEvent.waitfunction. (#846)v1.0.1Compare Source
v1.0.0Compare Source
From version 1.0 our async support is now optional, as the package has minimal dependencies by default.
For async support use either
pip install 'httpcore[asyncio]'orpip install 'httpcore[trio]'.The project versioning policy is now explicitly governed by SEMVER. See https://semver.org/.
pyca/pyopenssl (pyOpenSSL)
v24.1.0Compare Source
Backward-incompatible changes:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
OpenSSL.crypto.PKCS12andOpenSSL.crypto.NetscapeSPKI.OpenSSL.crypto.PKCS12may be replacedby the PKCS#12 APIs in the
cryptographypackage.Deprecations:
^^^^^^^^^^^^^
Changes:
^^^^^^^^
v24.0.0Compare Source
Backward-incompatible changes:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Deprecations:
^^^^^^^^^^^^^
Changes:
^^^^^^^^
OpenSSL.SSL.Connection.get_selected_srtp_profileto determine which SRTP profile was negotiated.#​1279 <https://github.com/pyca/pyopenssl/pull/1279>_.pytest-dev/pytest (pytest)
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 2am on saturday" 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.