Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency pluggy to v1.3.0 - autoclosed #63

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 17, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pluggy ==1.0.0 -> ==1.3.0 age adoption passing confidence

Release Notes

pytest-dev/pluggy (pluggy)

v1.3.0

Compare Source

=========================

Deprecations and Removals

  • #&#8203;426 <https://github.com/pytest-dev/pluggy/issues/426>_: Python 3.7 is no longer supported.

Features

  • #&#8203;428 <https://github.com/pytest-dev/pluggy/issues/428>_: Pluggy now exposes its typings to static type checkers.

    As part of this, the following changes are made:

    • Renamed _Result to Result, and exported as :class:pluggy.Result.
    • Renamed _HookRelay to HookRelay, and exported as :class:pluggy.HookRelay.
    • Renamed _HookCaller to HookCaller, and exported as :class:pluggy.HookCaller.
    • Exported HookImpl as :class:pluggy.HookImpl.
    • Renamed _HookImplOpts to HookimplOpts, and exported as :class:pluggy.HookimplOpts.
    • Renamed _HookSpecOpts to HookspecOpts, and exported as :class:pluggy.HookspecOpts.
    • Some fields and classes are marked Final and @final.
    • The :ref:api-reference is updated to clearly delineate pluggy's public API.

    Compatibility aliases are put in place for the renamed types.
    We do not plan to remove the aliases, but we strongly recommend to only import from pluggy.* to ensure future compatibility.

    Please note that pluggy is currently unable to provide strong typing for hook calls, e.g. pm.hook.my_hook(...),
    nor to statically check that a hook implementation matches the hook specification's type.

v1.2.0

Compare Source

=========================

Features

  • #&#8203;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 explicit wrapper=True designation in the @hookimpl() decorator.

v1.1.0

Compare Source

=====================

.. note::

This release was yanked because unfortunately the implicit new-style hook wrappers broke some downstream projects.
See #&#8203;403 <https://github.com/pytest-dev/pluggy/issues/403>__ for more information.
This was rectified in the 1.2.0 release.

Deprecations and Removals

  • #&#8203;364 <https://github.com/pytest-dev/pluggy/issues/364>_: Python 3.6 is no longer supported.

Features

  • #&#8203;260 <https://github.com/pytest-dev/pluggy/issues/260>_: Added "new-style" hook wrappers, a simpler but equally powerful alternative to the existing hookwrapper=True wrappers.

    New-style wrappers are generator functions, similarly to hookwrapper, but do away with the :class:result <pluggy.Result> object.
    Instead, the return value is sent directly to the yield statement, or, if inner calls raised an exception, it is raised from the yield.
    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:hookwrappers for the full documentation.

  • #&#8203;364 <https://github.com/pytest-dev/pluggy/issues/364>_: Python 3.11 and 3.12 are now officially supported.

  • #&#8203;394 <https://github.com/pytest-dev/pluggy/issues/394>_: Added the :meth:~pluggy.Result.force_exception method to _Result.

    force_exception allows (old-style) hookwrappers to force an exception or override/adjust an existing exception of a hook invocation,
    in a properly behaving manner. Using force_exception is 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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title chore(deps): update dependency pluggy to v1.2.0 chore(deps): update dependency pluggy to v1.3.0 Aug 26, 2023
@renovate renovate bot changed the title chore(deps): update dependency pluggy to v1.3.0 chore(deps): update dependency pluggy to v1.3.0 - autoclosed Sep 2, 2023
@renovate renovate bot closed this Sep 2, 2023
@renovate renovate bot deleted the renovate/pluggy-1.x branch September 2, 2023 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants