[AUH] python3-packaging: upgrading to 26.3 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe(s) *python3-packaging* to *26.3* has Succeeded.

Next steps:
    - apply the patch: git am 0001-python3-packaging-upgrade-26.2-26.3.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 fd436f9d7f52f56b2f1d832bb6162feddc954eb9 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@yoctoproject.org>
Date: Wed, 5 Aug 2026 05:38:00 +0000
Subject: [PATCH] python3-packaging: upgrade 26.2 -> 26.3

Source: CHANGELOG.rst

26.3 - 2026-08-03
~~~~~~~~~~~~~~~~~

Features:

* Add a public :class:`~packaging.ranges.VersionRange` API and
  :meth:`SpecifierSet.to_range() <packaging.specifiers.SpecifierSet.to_range>`,
  representing the versions a specifier set accepts as an interval set that
  supports intersection, union, difference, complement, set relations,
  membership tests, and filtering.
  :meth:`~packaging.ranges.VersionRange.to_specifier_set` converts a range back
  to a :class:`~packaging.specifiers.SpecifierSet` where a PEP 440 form exists.
  (:pull:`1267`, :pull:`1270`, :pull:`1298`)
* PEP 808: accept ``Metadata-Version: 2.6``. (:pull:`1194`)
* Add a ``limit`` argument to ``parse_tag()`` for compressed tag sets.
  (:issue:`1220`)
* Add a ``prefer_sdist_predicate`` argument to ``Pylock.select()`` to prefer
  source distributions over wheels for selected packages. (:pull:`1334`)
* Add :func:`~packaging.tags.pure_python_tags` to generate the pure-Python
  tags for a Python version without touching the running platform.
  (:pull:`1346`)
* Add :meth:`SpecifierSet.is_subset()
  <packaging.specifiers.SpecifierSet.is_subset>`, :meth:`~packaging.specifiers.SpecifierSet.is_superset`,
  and :meth:`~packaging.specifiers.SpecifierSet.is_disjoint`, which compare the
  versions two specifier sets accept. (:pull:`1313`)

Behavior adaptations:

* Drop support for Python 3.8; packaging now requires Python 3.9 or later.
  (:pull:`1157`)
* Prefer native ``linux_*`` platform tags over ``manylinux`` and ``musllinux``
  tags on Linux. (:issue:`160`)

Fixes for versions and specifiers:

* Raise ``InvalidVersion`` instead of ``TypeError`` when ``Version`` is given a
  non-string. (:pull:`1319`)
* Raise ``InvalidVersion`` for non-string pre-release letters passed to
  ``Version.from_parts``. (:pull:`1241`)
* Fix an ``AttributeError`` when hashing internally trimmed versions.
  (:pull:`1242`)
* Fix ``SpecifierSet.is_unsatisfiable`` for post-release boundary
  intersections. (:pull:`1257`)

Fixes for requirements and markers:

* Make ``Requirement.__hash__`` consistent with ``__eq__`` for
  trailing-zero-equivalent specifiers (e.g. ``foo==1.0.0`` and
  ``foo==1.0.0.0``), so equal requirements hash equal and deduplicate in
  sets and dicts. (:pull:`1232`)
* Normalize requested extra names before comparing or hashing requirements.
  (:issue:`644`)
* Preserve a ``Requirement``'s specifier ``prereleases`` override across a
  pickle round trip. (:issue:`1204`)
* Raise ``InvalidRequirement`` instead of ``InvalidSpecifier`` when a
  requirement contains an invalid specifier. (:pull:`1332`)
* Clarify the error for post-release prefix wildcards like ``==1.0.post1.*``.
  (:pull:`1299`)
* Preserve quoting semantics when serializing marker values, so round-tripped
  markers parse back to the same marker. (:pull:`1213`)
* Keep the parentheses of a nested group when serializing markers.
  (:pull:`1316`)
* Normalize ``extra`` and ``dependency_groups`` values in nested markers at

[Changelog truncated as it exceeds 3000 characters;
the full changelog can be found in an attachment to the AUH email]
---
 .../{python3-packaging_26.2.bb => python3-packaging_26.3.bb}    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-packaging_26.2.bb => python3-packaging_26.3.bb} (94%)