Update dependency pluggy to v1.2.0 #51
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/pluggy-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
==1.0.0->==1.2.0Release Notes
pytest-dev/pluggy
v1.2.0Compare Source
=========================
Features
#​405 <https://github.com/pytest-dev/pluggy/issues/405>_: The new-style hook wrappers, added in the yanked 1.1.0 release, now require an explicitwrapper=Truedesignation in the@hookimpl()decorator.v1.1.0Compare Source
=====================
.. note::
This release was yanked because unfortunately the implicit new-style hook wrappers broke some downstream projects.
See
#​403 <https://github.com/pytest-dev/pluggy/issues/403>__ for more information.This was rectified in the 1.2.0 release.
Deprecations and Removals
#​364 <https://github.com/pytest-dev/pluggy/issues/364>_: Python 3.6 is no longer supported.Features
#​260 <https://github.com/pytest-dev/pluggy/issues/260>_: Added "new-style" hook wrappers, a simpler but equally powerful alternative to the existinghookwrapper=Truewrappers.New-style wrappers are generator functions, similarly to
hookwrapper, but do away with the :class:result <pluggy._callers._Result>object.Instead, the return value is sent directly to the
yieldstatement, or, if inner calls raised an exception, it is raised from theyield.The wrapper is expected to return a value or raise an exception, which will become the result of the hook call.
New-style wrappers are fully interoperable with old-style wrappers.
We encourage users to use the new style, however we do not intend to deprecate the old style any time soon.
See :ref:
hookwrappersfor the full documentation.#​364 <https://github.com/pytest-dev/pluggy/issues/364>_: Python 3.11 and 3.12 are now officially supported.#​394 <https://github.com/pytest-dev/pluggy/issues/394>_: Added the :meth:~pluggy._callers._Result.force_exceptionmethod to_Result.force_exceptionallows (old-style) hookwrappers to force an exception or override/adjust an existing exception of a hook invocation,in a properly behaving manner. Using
force_exceptionis preferred over raising an exception from the hookwrapper,because raising an exception causes other hookwrappers to be skipped.
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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.
Kudos, SonarCloud Quality Gate passed!