From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <leon.anavi@konsulko.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [[PATCHv2] python3-pyzstd: Upgrade 0.17.0 -> 0.19.1
Date: Wed, 28 Jan 2026 18:03:35 +0100 [thread overview]
Message-ID: <DG0DVCEFA5HX.L3N59E48OKKP@bootlin.com> (raw)
In-Reply-To: <20260127091829.3500551-1-leon.anavi@konsulko.com>
On Tue Jan 27, 2026 at 10:18 AM CET, Leon Anavi via lists.openembedded.org wrote:
> Upgrade to release 0.19.1:
>
> - Fix SeekableZstdFile write table entries on 32-bits architectures
> when there is a huge number of entries
>
> From release 0.19.0:
>
> - The project has been completely refactored to use the Zstandard
> implementation from the standard library (PEP-784)
> - The refactor has some minor impact on public APIs, such as
> changing the exception raised on invalid input
> - Add backports.zstd dependency for Python before 3.14
> - Changes in build dependency: remove setuptools and C build
> toolchain, add hatchling and hatch-vcs
> - Remove git submodule usage
> - Drop support for Python 3.9 and below
> - Use ruff as formatter and linter
> - Embed type hints in Python code, and check with mypy
>
> All ptests pass following python3 upgrade from 3.13.11 to 3.14.0.
>
> Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
> ---
Hi Leon,
Thanks for the new version.
It looks like this is breaking some ptest:
Failed ptests:
{'python3-pyzstd': 'START: ptest-runner\n'
'2026-01-28T16:27\n'
'\n'
...
"E ImportError: cannot import name 'zstd' from "
"'compression' (unknown location)\n"
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/2996
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/1005
Test results can be found here:
https://valkyrie.yocto.io/pub/non-release/20260128-86/testresults/qemux86-64-ptest/core-image-ptest-python3-pyzstd/
Test results for riscv64 and arm64 are not published at this time, as
some tests are still running. They will all end-up in https://valkyrie.yocto.io/pub/non-release/20260128-86/testresults/
Can you have a look at these failures?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-01-28 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 9:18 [[PATCHv2] python3-pyzstd: Upgrade 0.17.0 -> 0.19.1 Leon Anavi
2026-01-28 17:03 ` Mathieu Dubois-Briand [this message]
2026-01-29 11:22 ` [OE-core] " Leon Anavi
2026-01-31 9:09 ` Mathieu Dubois-Briand
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=DG0DVCEFA5HX.L3N59E48OKKP@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=leon.anavi@konsulko.com \
--cc=openembedded-core@lists.openembedded.org \
/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