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 #148

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 25, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pluggy ==0.13.1 -> ==1.5.0 age adoption passing confidence

Release Notes

pytest-dev/pluggy (pluggy)

v1.5.0

Compare Source

v1.4.0

Compare Source

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

Features

  • #&#8203;463 <https://github.com/pytest-dev/pluggy/issues/463>_: A warning :class:~pluggy.PluggyTeardownRaisedWarning is now issued when an old-style hookwrapper raises an exception during teardown.
    See the warning documentation for more details.

  • #&#8203;471 <https://github.com/pytest-dev/pluggy/issues/471>_: Add :func:PluginManager.unblock <pluggy.PluginManager.unblock> method to unblock a plugin by plugin name.

Bug Fixes

  • #&#8203;441 <https://github.com/pytest-dev/pluggy/issues/441>_: Fix :func:~pluggy.HookCaller.call_extra() extra methods getting ordered before everything else in some circumstances. Regressed in pluggy 1.1.0.

  • #&#8203;438 <https://github.com/pytest-dev/pluggy/issues/438>_: Fix plugins registering other plugins in a hook when the other plugins implement the same hook itself. Regressed in pluggy 1.1.0.

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.

v1.0.0

Compare Source

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

Deprecations and Removals

  • #&#8203;116 <https://github.com/pytest-dev/pluggy/issues/116>_: Remove deprecated implprefix support.
    Decorate hook implementations using an instance of HookimplMarker instead.
    The deprecation was announced in release 0.7.0.

  • #&#8203;120 <https://github.com/pytest-dev/pluggy/issues/120>_: Remove the deprecated proc argument to call_historic.
    Use result_callback instead, which has the same behavior.
    The deprecation was announced in release 0.7.0.

  • #&#8203;265 <https://github.com/pytest-dev/pluggy/issues/265>_: Remove the _Result.result property. Use _Result.get_result() instead.
    Note that unlike result, get_result() raises the exception if the hook raised.
    The deprecation was announced in release 0.6.0.

  • #&#8203;267 <https://github.com/pytest-dev/pluggy/issues/267>_: Remove official support for Python 3.4.

  • #&#8203;272 <https://github.com/pytest-dev/pluggy/issues/272>_: Dropped support for Python 2.
    Continue to use pluggy 0.13.x for Python 2 support.

  • #&#8203;308 <https://github.com/pytest-dev/pluggy/issues/308>_: Remove official support for Python 3.5.

  • #&#8203;313 <https://github.com/pytest-dev/pluggy/issues/313>_: The internal pluggy.callers, pluggy.manager and pluggy.hooks are now explicitly marked private by a _ prefix (e.g. pluggy._callers).
    Only API exported by the top-level pluggy module is considered public.

  • #&#8203;59 <https://github.com/pytest-dev/pluggy/issues/59>_: Remove legacy __multicall__ recursive hook calling system.
    The deprecation was announced in release 0.5.0.

Features

  • #&#8203;282 <https://github.com/pytest-dev/pluggy/issues/282>_: When registering a hookimpl which is declared as hookwrapper=True but whose
    function is not a generator function, a :class:~pluggy.PluginValidationError exception is
    now raised.

    Previously this problem would cause an error only later, when calling the hook.

    In the unlikely case that you have a hookwrapper that returns a generator
    instead of yielding directly, for example:

    .. code-block:: python

    def my_hook_implementation(arg):
        print("before")
        yield
        print("after")
    
    @&#8203;hookimpl(hookwrapper=True)
    def my_hook(arg):
        return my_hook_implementation(arg)
    

    change it to use yield from instead:

    .. code-block:: python

    @&#8203;hookimpl(hookwrapper=True)
    def my_hook(arg):
        yield from my_hook_implementation(arg)
    
  • #&#8203;309 <https://github.com/pytest-dev/pluggy/issues/309>_: Add official support for Python 3.9.

  • #&#8203;251 <https://github.com/pytest-dev/pluggy/issues/251>_: Add specname option to @hookimpl. If specname is provided, it will be used
    instead of the function name when matching this hook implementation to a hook specification during registration (allowing a plugin to register
    a hook implementation that was not named the same thing as the corresponding @hookspec).


Configuration

πŸ“… Schedule: Branch creation - "after 10pm every weekday,every weekend" in timezone Africa/Lusaka, 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.

@codecov-commenter
Copy link

codecov-commenter commented Mar 17, 2023

Codecov Report

All modified and coverable lines are covered by tests βœ…

Project coverage is 93.77%. Comparing base (9bb92a1) to head (339bfde).

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #148      +/-   ##
==========================================
+ Coverage   93.36%   93.77%   +0.41%     
==========================================
  Files          18       18              
  Lines         241      241              
==========================================
+ Hits          225      226       +1     
+ Misses         16       15       -1     

β˜” View full report in Codecov by Sentry.
πŸ“’ Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/pluggy-1.x branch 3 times, most recently from fbdde5f to cfbae78 Compare June 21, 2023 11:52
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.

None yet

1 participant