Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <tim.orling@konsulko.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 3/9] python3-packaging: upgrade 26.0 -> 26.2
Date: Sun, 31 May 2026 19:30:33 +0200	[thread overview]
Message-ID: <DIX1H01XXHMQ.3EYWKQXBXFXPB@bootlin.com> (raw)
In-Reply-To: <20260531001756.1582306-3-tim.orling@konsulko.com>

On Sun May 31, 2026 at 2:17 AM CEST, Tim Orling via lists.openembedded.org wrote:
> From: Tim Orling <tim.orling@konsulko.com>
>
> 26.2 - 2026-04-24
> Fixes:
> * Fix incorrect sysconfig var name for pyemscripten in (PR #1160)
> * Make Version, Specifier, SpecifierSet, Tag, Marker, and Requirement
>   pickle-safe and backward-compatible with pickles created in 25.0-26.1
>   (including references to the removed packaging._structures module)
>   (PR #1163, PR #1168, PR #1170, PR #1171)
> * Re-export ExceptionGroup in metatadata for now in (PR #1164)
>
> 26.1 - 2026-04-14
> Fixes:
> * Fix > comparison for versions with dev+local segments in (PR #1097)
> * Fix incorrect self-comparison for InfinityType and NegativeInfinityType
>   in (PR #1093)
> * Canonicalize when deduplicating specifiers in SpecifierSet in
>   (PR #1109)
> * Fix charset error message formatting in (PR #1121)
> * Handle the key parameter in SpecifierSet.filter when specifiers are
>   empty and prerelease is False in (PR #1096)
> * Standardize inner components of repr output in (PR #1090)
> * Specifier’s === uses original string, not normalized, when available
>   in (PR #1124)
> * Propagate int-max-str-digits ValueError in (PR #1155)
>
> For additional changes, see [1].
> For full comparison, see [2].
>
> [1] https://packaging.pypa.io/en/stable/changelog.html
> [2] https://github.com/pypa/packaging/compare/26.0...26.2
>
> Signed-off-by: Tim Orling <tim.orling@konsulko.com>
> ---

Hi Tim,

Thanks for the upgrade.

We get a ptest failure on python3-packaging:

Failed ptests:
{'python3-packaging': 'START: ptest-runner\n'
                      '2026-05-31T14:34\n'
                      '\n'
                      'ImportError while importing test module '
                      "'/usr/lib/python3-packaging/ptest/tests/property/test_specifier_comparison.py'.\n"
                      'Hint: make sure your test modules/packages have valid '
                      'Python names.\n'
                      'Traceback:\n'
                      '../../python3.14/importlib/__init__.py:88: in '
                      'import_module\n'
                      '    return _bootstrap._gcd_import(name[level:], '
                      'package, level)\n'
                      '           '
                      '^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n'
                      'tests/property/test_specifier_comparison.py:8: in '
                      '<module>\n'
                      '    from hypothesis import assume, given\n'
                      "E   ModuleNotFoundError: No module named 'hypothesis'\n"

https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/1658
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/3723
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/3741
https://autobuilder.yoctoproject.org/valkyrie/#/builders/109/builds/472
https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/456

Can you have look at the issue?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-05-31 17:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-31  0:17 [PATCH 1/9] at-spi2-core: upgrade 2.60.3 -> 2.60.4 tim.orling
2026-05-31  0:17 ` [PATCH 2/9] python3-certifi: upgrade 2026.4.22 -> 2026.5.20 tim.orling
2026-05-31  0:17 ` [PATCH 3/9] python3-packaging: upgrade 26.0 -> 26.2 tim.orling
2026-05-31 17:30   ` Mathieu Dubois-Briand [this message]
2026-05-31 20:09   ` [PATCH] " tim.orling
2026-05-31  0:17 ` [PATCH 4/9] python3-poetry-core: upgrade 2.3.2 -> 2.4.1 tim.orling
2026-05-31  0:17 ` [PATCH 5/9] python3-pytz: upgrade 2026.1 -> 2026.2 tim.orling
2026-05-31  0:31   ` Patchtest results for " patchtest
2026-05-31  0:17 ` [PATCH 6/9] python3-rpds-py: upgrade 0.30.0 -> 2026.5.1 tim.orling
2026-05-31  0:17 ` [PATCH 7/9] python3-snowballstemmer: upgrade 3.0.1 -> 3.1.0 tim.orling
2026-05-31  0:17 ` [PATCH 8/9] python3-wcwidth: upgrade 0.6.0 -> 0.7.0 tim.orling
2026-05-31  0:31   ` Patchtest results for " patchtest
2026-05-31  0:17 ` [PATCH 9/9] python3-zipp: upgrade 3.23.1 -> 4.1.0 tim.orling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DIX1H01XXHMQ.3EYWKQXBXFXPB@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tim.orling@konsulko.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox