From patchwork Fri Oct 16 06:03:18 2026 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: auh@yoctoproject.org X-Patchwork-Id: 101010 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 27AC4CCA490 for ; Fri, 16 Oct 2026 06:03:22 +0000 (UTC) Received: from a27-191.smtp-out.us-west-2.amazonses.com (a27-191.smtp-out.us-west-2.amazonses.com [54.240.27.191]) by mx.groups.io with SMTP id smtpd.msgproc02-g2.15770.1792130598954709477 for ; Thu, 15 Oct 2026 23:03:19 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@yoctoproject.org header.s=lvjh2tk576v2ro5mi6k4dt3mc6wpqbky header.b=TGu3Eb5S; dkim=pass header.i=@amazonses.com header.s=hsbnp7p3ensaochzwyq5wwmceodymuwv header.b=jp4/1IKR; spf=pass (domain: us-west-2.amazonses.com, ip: 54.240.27.191, mailfrom: 010101a1434ec4bd-05ca3c08-423d-4f34-b5e6-fe8e44feaa64-000000@us-west-2.amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=lvjh2tk576v2ro5mi6k4dt3mc6wpqbky; d=yoctoproject.org; t=1792130598; h=Content-Type:MIME-Version:From:To:Cc:Subject:Message-Id:Date; bh=hD4qmXXTHADwXY5D6wrm1OYV1Qurj14eZTwKvB2CGzY=; b=TGu3Eb5SMqlS5HDdBSuxBVLB6SVRrXuoPqm9CS380/XIxkM1YLu2Q3BQgZSGkbUf unpNp/SVbomHv2v7fXimL0Kp41VRiEylW+EomddnfnXZnqoxre9glIPd5GgNOxcDDqm GIj/KInuBgJFz2kZCzRQy6jPo/kzp9vjROo8QVSM= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=hsbnp7p3ensaochzwyq5wwmceodymuwv; d=amazonses.com; t=1792130598; h=Content-Type:MIME-Version:From:To:Cc:Subject:Message-Id:Date:Feedback-ID; bh=hD4qmXXTHADwXY5D6wrm1OYV1Qurj14eZTwKvB2CGzY=; b=jp4/1IKROTTB+YtlX8xKEZa24qbq1hTRCxjisnJR0f1ZoHAJhWXXmRy2hLeeLdHi Og48qzY59iB+yugRNLugMgvagEpEXjUNr3Z0AAydJnsiO4tgB5nsk3CKvvrDmO2bUuE qz12+iyQ4vsVkNQ9cc7Gd4IiLnSdSXLBOZhlz2jw= MIME-Version: 1.0 From: auh@yoctoproject.org To: Tim Orling Cc: openembedded-core@lists.openembedded.org Subject: [AUH] python3-pluggy: upgrading to 1.7.0 SUCCEEDED Message-ID: <010101a1434ec4bd-05ca3c08-423d-4f34-b5e6-fe8e44feaa64-000000@us-west-2.amazonses.com> Date: Fri, 16 Oct 2026 06:03:18 +0000 Feedback-ID: ::1.us-west-2.9np3MYPs3fEaOBysGKSlUD4KtcmPijcmS9Az2Hwf7iQ=:AmazonSES X-SES-Outgoing: 2026.10.16-54.240.27.191 List-Id: X-Webhook-Received: from 45-33-107-173.ip.linodeusercontent.com [45.33.107.173] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Fri, 16 Oct 2026 06:03:22 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/247963 Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *python3-pluggy* to *1.7.0* has Succeeded. Next steps: - apply the patch: git am 0001-python3-pluggy-upgrade-1.6.0-1.7.0.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -- >8 -- From 4627cc9f626c65bd9937cd1f59ec5e51797eee73 Mon Sep 17 00:00:00 2001 From: Upgrade Helper Date: Fri, 16 Oct 2026 05:44:36 +0000 Subject: [PATCH] python3-pluggy: upgrade 1.6.0 -> 1.7.0 pluggy 1.7.0 (2026-10-14) ========================= Deprecations and Removals ------------------------- - `#632 < >`_: Hookspec methods defined without ``self`` as the first parameter now emit a :class:`DeprecationWarning`. Add ``self`` as the first parameter or use ``@staticmethod``. Features -------- - `#170 < >`_: Hookspecs can now declare default values for arguments, using the usual ``def myhook(myarg="default")`` syntax. This is mainly a backward compatibility feature, to allow a hookspec to add new parameters to an existing hook without breaking existing *callers*. See :ref:`hookspec_arg_default` for details. - `#729 < >`_: Tracing now adds detail where ``str()`` is ambiguous: empty strings and strings containing whitespace are quoted, and enums and paths show their ``repr()``. A value spanning several lines is now displayed as a block instead of running into the surrounding trace. Bug Fixes --------- - `#629 < >`_: Fix hooks failing to register on Python 3.14+ when type annotations use forward references. - `#315 < >`_: Source archives created by ``git archive`` (including GitHub's "Source code" downloads) now carry version information, so building pluggy from them no longer fails with a missing version. - `#442 < >`_: With the addition of default values for hookspec arguments, we also changed the precedence of default values for *hookimpl* arguments. Previously, if a hookimpl function declared a default for an argument, it was always used, even if the *hook call* passed an explicit value. Now the precedence is changed to: hook call passed value > hookspec default value > hookimpl default value. See :ref:`hookimpl_arg_defaults`. - `#701 < >`_: Hookimpls and hookspecs are now discovered via :func:`inspect.getattr_static`, so properties, ``cached_property`` and other descriptors are no longer executed while scanning a plugin. Hooks declared through such a descriptor are not supported. As a side effect, ``@hookimpl``/``@hookspec`` applied *above* ``@classmethod`` or ``@staticmethod`` is now picked up; previously the marker sat on the wrapper where ``getattr()`` never saw it. Callables stored directly on a plugin instance -- in its ``__dict__`` or in a ``__slots__`` slot -- keep being called exactly as ``getattr()`` returned them, i.e. without an implicit ``self``. - `#431 < >`_: Fix ``HookCaller._remove_plugin()`` to remove all hook implementations for a plugin in a single call, instead of only the first one. Also fix ``PluginManager.get_hookcallers()`` to not return duplicate ``HookCaller`` entries when a plugin has multiple implementations on the same hook (e.g. via ``specname``). - `#695 < >`_: Fixed :func:`~pluggy.PluginManager.subset_hook_caller()` not excluding removed plugins which use :func:`@hookiml(specname="...") `. - `#424 < >`_: Tracing no longer breaks hook execution when a traced object has a broken ``__repr__`` or ``__str__``. Such a value is now rendered as ``<[RuntimeError(...) raised in str()] Broken object at 0x...>``, in the same style pytest uses for unpresentable objects, instead of propagating the exception out of the hook call. - `#681 < >`_: Tracing no longer crashes with ``UnicodeEncodeError`` when a hook argument or return value contains lone surrogates; they are escaped with ``backslashreplace`` before the message reaches the writer. Trace output is otherwise unchanged. - `#727 < >`_: Fix the warning for hookspec arguments missing from a hook call being attributed to pluggy's own frame instead of to the code making the call. This affected ``HookCaller.__call__``, ``call_historic`` and ``call_extra``. - `#731 < >`_: :func:`PluginManager.register(None) ` is now ignored instead of having some weird behaviors. - `#733 < >`_: :meth:`PluginManager.register() ` now validates all hook implementations of a plugin before registering any of them, so a plugin that fails validation no longer stays partially registered. - `#755 < >`_: Skip already registered entry-point plugins without evaluating the plugin object's truthiness. - `#757 < >`_: Restore the project URLs in the package metadata, which were lost in pluggy 1.6.0 when the packaging configuration moved to ``pyproject.toml``. Links to the documentation, changelog, issue tracker and funding page were added as well. - `#759 < >`_: :meth:`PluginManager.unregister() ` now raises :exc:`ValueError` when both ``plugin`` and ``name`` are given but refer to different plugins, instead of removing one plugin's hook implementations and another plugin's registry entry. It also fully unregisters plugin objects that are falsy (e.g. define ``__len__`` returning ``0``); previously their name stayed in the registry. - `#186 < >`_: Fixed broken external documentation references in [Changelog truncated as it exceeds 5000 characters; the full changelog can be found in an attachment to the AUH email] --- .../python/{python3-pluggy_1.6.0.bb => python3-pluggy_1.7.0.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-devtools/python/{python3-pluggy_1.6.0.bb => python3-pluggy_1.7.0.bb} (80%) diff --git a/meta/recipes-devtools/python/python3-pluggy_1.6.0.bb b/meta/recipes-devtools/python/python3-pluggy_1.7.0.bb similarity index 80% rename from meta/recipes-devtools/python/python3-pluggy_1.6.0.bb rename to meta/recipes-devtools/python/python3-pluggy_1.7.0.bb index b8e4bbc75b..55d6383fa1 100644 --- a/meta/recipes-devtools/python/python3-pluggy_1.6.0.bb +++ b/meta/recipes-devtools/python/python3-pluggy_1.7.0.bb @@ -3,7 +3,7 @@ HOMEPAGE = "https://github.com/pytest-dev/pluggy" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://LICENSE;md5=1c8206d16fd5cc02fa9b0bb98955e5c2" -SRC_URI[sha256sum] = "7dcc130b76258d33b90f61b658791dede3486c3e6bfb003ee5c9bfb396dd22f3" +SRC_URI[sha256sum] = "d1eaa46ebb595891b860ab086b4d09c8588af65ebd4361b8e8f4bb8920b90ba8" DEPENDS += "python3-setuptools-scm-native"