Update dependency pluggy to v1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pluggy	==0.13.1 -> ==1.0.0

---

Release Notes

pytest-dev/pluggy

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 PluggyValidationError 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_real_implementation(arg):
      print("before")
      yield
      print("after")
  
  @​hookimpl(hookwrapper=True)
  def my_hook(arg):
      return my_hook_implementation(arg)
  

  change it to use yield from instead:

  .. code-block:: python

  @​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 - 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]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.