From: tim.orling@konsulko.com
To: openembedded-devel@lists.openembedded.org
Subject: [meta-python][PATCH 0/3] Upgrade python3-orjson and enable ptest
Date: Thu, 29 Jan 2026 17:07:34 -0800 [thread overview]
Message-ID: <cover.1769715106.git.tim.orling@konsulko.com> (raw)
From: Tim Orling <tim.orling@konsulko.com>
This series upgrades python3-orjson to 3.11.6 and patches it to support
building on non-x86* architectures like riscv64 and arm64.
7 of the ptests are skipped because of missing python3-pendulum, but it does
not yet support python 3.14.x
Tested on qemux86-64, qemuriscv64 and qemuarm64.
The following changes since commit 7bbe4a4e200452b1fd6c09c7fcf36c4b229146f6:
php: upgrade 8.5.1 -> 8.5.2 (2026-01-20 14:35:59 -0800)
are available in the Git repository at:
https://git.openembedded.org/meta-openembedded-contrib timo/python3-orjson-3.11.6
https://git.openembedded.org/meta-openembedded-contrib/log/?h=timo/python3-orjson-3.11.6
for you to fetch changes up to ecd3b46d0c63b03fc434ee3763292acab1463941:
python3-orjson: use git fetcher; enable ptest (2026-01-29 11:26:47 -0800)
----------------------------------------------------------------
Tim Orling (3):
python3-orjson: upgrade 3.10.17 -> 3.11.6
python3-faker: add v40.1.2
python3-orjson: use git fetcher; enable ptest
.../ptest-packagelists-meta-python.inc | 2 +
.../python/python3-faker_40.1.2.bb | 45 +
.../python/python3-orjson-crates.inc | 2243 ++++++++++++++++-
...rd-avx512-module-with-x86-target-cfg.patch | 37 +
...e-detection-macro-in-pystrref-object.patch | 34 +
.../python/python3-orjson_3.10.17.bb | 22 -
.../python/python3-orjson_3.11.6.bb | 45 +
7 files changed, 2357 insertions(+), 71 deletions(-)
create mode 100644 meta-python/recipes-devtools/python/python3-faker_40.1.2.bb
create mode 100644 meta-python/recipes-devtools/python/python3-orjson/0001-Guard-avx512-module-with-x86-target-cfg.patch
create mode 100644 meta-python/recipes-devtools/python/python3-orjson/0002-Guard-x86-feature-detection-macro-in-pystrref-object.patch
delete mode 100644 meta-python/recipes-devtools/python/python3-orjson_3.10.17.bb
create mode 100644 meta-python/recipes-devtools/python/python3-orjson_3.11.6.bb
--
2.43.0
next reply other threads:[~2026-01-30 1:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 1:07 tim.orling [this message]
2026-01-30 1:07 ` [meta-python][PATCH 1/3] python3-orjson: upgrade 3.10.17 -> 3.11.6 tim.orling
2026-01-30 1:07 ` [meta-python][PATCH 2/3] python3-faker: add v40.1.2 tim.orling
2026-01-30 1:07 ` [meta-python][PATCH 3/3] python3-orjson: use git fetcher; enable ptest tim.orling
2026-01-30 14:57 ` [oe] [meta-python][PATCH 0/3] Upgrade python3-orjson and " Tim Orling
2026-02-03 19:13 ` [meta-python][PATCH v2 v2 0/6] " tim.orling
2026-02-03 19:13 ` [meta-python][PATCH v2 v2 1/6] python3-orjson: upgrade 3.10.17 -> 3.11.6 tim.orling
2026-02-03 19:13 ` [meta-python][PATCH v2 v2 2/6] python3-faker: add v40.1.2 tim.orling
2026-02-03 19:13 ` [meta-python][PATCH v2 v2 3/6] python3-tokenize-rt: add at v6.2.0 tim.orling
2026-02-03 19:13 ` [meta-python][PATCH v2 v2 4/6] python3-time-machine: add at v3.2.0 tim.orling
2026-02-03 19:13 ` [meta-python][PATCH v2 v2 5/6] python3-pendulum: " tim.orling
2026-02-03 19:13 ` [meta-python][PATCH v2 v2 6/6] python3-orjson: use git fetcher; enable ptest 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=cover.1769715106.git.tim.orling@konsulko.com \
--to=tim.orling@konsulko.com \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.