Log message:
py-*: remove unused tool dependency

py-setuptools includes the py-wheel functionality nowadays

Log message:
py-pluggy: updated to 1.5.0

pluggy 1.5.0 (2024-04-19)

Features
- Add support for deprecating specific hook parameters, or more generally, for \ 
issuing a warning whenever a hook implementation requests certain parameters.
  See :ref:`warn_on_impl` for details.

Bug Fixes
- ``PluginManager.get_plugins()`` no longer returns ``None`` for blocked plugins.

Log message:
py-pluggy: updated to 1.4.0

pluggy 1.4.0 (2024-01-24)

Features

- 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.
- Add :func:`PluginManager.unblock <pluggy.PluginManager.unblock>` method \ 
to unblock a plugin by plugin name.

Bug Fixes

- Fix :func:`~pluggy.HookCaller.call_extra()` extra methods getting ordered \ 
before everything else in some circumstances. Regressed in pluggy 1.1.0.
- Fix plugins registering other plugins in a hook when the other plugins \ 
implement the same hook itself. Regressed in pluggy 1.1.0.

Log message:
py-pluggy: updated to 1.3.0

pluggy 1.3.0 (2023-08-26)
=========================

Deprecations and Removals
-------------------------

- Python 3.7 is no longer supported.

Features
--------

- 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.

Log message:
Remove dependencies for Python 3.7

Log message:
py-pluggy: update to 1.2.0.

pluggy 1.2.0 (2023-06-21)
=========================

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 explicit \ 
``wrapper=True`` designation in the ``@hookimpl()`` decorator.

pluggy 1.1.0 (YANKED)
=====================

.. 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 existing ``hookwrapper=True`` wrappers.

  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 ``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.

- `#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_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.

Log message:
Mass-change BUILD_DEPENDS to TOOL_DEPENDS outside mk/.

Almost all uses, if not all of them, are wrong, according to the
semantics of BUILD_DEPENDS (packages built for target available for
use _by_ tools at build-time) and TOOL_DEPEPNDS (packages built for
host available for use _as_ tools at build-time).

No change to BUILD_DEPENDS as used correctly inside buildlink3.

As proposed on tech-pkg:
https://mail-index.netbsd.org/tech-pkg/2023/06/03/msg027632.html

Log message:
*: use PYTHON_VERSION instead of _PYTHON_VERSION