From: "Thomas Roos" <roosesweb@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Thomas Roos <thomas@roosesweb.de>
Subject: [meta-python][PATCH 0/6] Fixes for pika, pint, haversine and httpx2
Date: Sun, 8 Nov 2026 20:25:43 +0100 [thread overview]
Message-ID: <20261108192549.1082715-1-thomas@roosesweb.de> (raw)
Four recipes in meta-python install broken or wrong code. I found them
while upgrading meta-homeassistant to Home Assistant 2026.11, but the
fixes do not depend on that:
- python3-pika: the 1.4.4 upgrade only changed the unused sha256sum, so
SRCREV still pointed at a 1.4.2 era commit and the package installed
pika 1.4.2 under version 1.4.4. SRCREV now points at the 1.4.4 tag
commit, and tag=${PV} lets the fetcher check that.
- python3-pint: flexcache, flexparser and typing-extensions were only
pulled in by the ptest, so "import pint" failed on an image without
the ptest. flexcache and flexparser are extended to native and
nativesdk like pint; without that, python3-pint-native fails with
"Nothing RPROVIDES 'python3-flexcache-native'".
- python3-haversine: numba is optional, but haversine only catches
ModuleNotFoundError. numba 0.66 (meta-python-ai) raises ImportError with
NumPy 2.5, which broke "import haversine". The patch catches ImportError.
Submitted upstream: https://github.com/mapado/haversine/pull/91
- python3-httpx2, with the new python3-truststore and python3-httpcore2:
httpx2 requires httpcore2, anyio and truststore, but did not depend on
them, so "import httpx2" failed with "No module named 'httpcore2'".
The series is independent of the "Python updates for Home Assistant
2026.11" series sent at the same time; both apply to master on their own.
Related changes for the Home Assistant 2026.11 upgrade:
- openembedded-core: python3-cython 3.2.9 -> 3.3.1
https://github.com/thomas-roos/openembedded-core/commits/ha-2026.11
- meta-openembedded (meta-python): this series and the updates series
https://github.com/thomas-roos/meta-openembedded/commits/ha-2026.11
- meta-python-ai: 7 upgrades
https://github.com/zboszor/meta-python-ai/pull/46
- meta-homeassistant: Home Assistant 2026.3.1 -> 2026.11.0
https://github.com/meta-homeassistant/meta-homeassistant/pull/207
Testing, on top of master b5d60afb63:
- built for qemux86-64 (x86-64-v3), together with meta-homeassistant's
core-image-homeassistant (Home Assistant 2026.11)
- ptests pass for flexcache, flexparser and pint
- in the running image, Home Assistant starts (it imports httpx2) and
all its integrations import, including the geo_rss_events and geojson
based ones that import haversine
- python3-pika: built; the installed dist-info now reports 1.4.4. It is
not in a ptest list of meta-python, so its ptest was not run
- checked with bodnuti: patchtest pass, no oelint-adv or shellcheck
findings
AI disclosure: the patches, commit messages and this cover letter were
written with Claude Code (Claude Opus 5.5), as the AI-Generated tags in
each patch say. I reviewed every change, ran the builds and tests above,
and can answer for them.
Thomas Roos (6):
python3-pika: build the 1.4.4 release
python3-pint: add missing runtime dependencies
python3-haversine: keep working when numba fails to import
python3-truststore: add recipe
python3-httpcore2: add recipe
python3-httpx2: add missing runtime dependencies
.../python/python3-flexcache_0.3.bb | 2 +
.../python/python3-flexparser_0.4.bb | 2 +
...-pure-Python-kernels-if-numba-fails-.patch | 40 +++++++++++++++++++
.../python/python3-haversine_2.9.0.bb | 1 +
.../python/python3-httpcore2_2.16.0.bb | 26 ++++++++++++
.../python/python3-httpx2_2.16.0.bb | 5 ++-
.../python/python3-pika_1.4.4.bb | 6 +--
.../python/python3-pint_0.26.2.bb | 5 ++-
.../python/python3-truststore_0.10.4.bb | 13 ++++++
9 files changed, 93 insertions(+), 7 deletions(-)
create mode 100644 meta-python/recipes-devtools/python/python3-haversine/0001-Fall-back-to-the-pure-Python-kernels-if-numba-fails-.patch
create mode 100644 meta-python/recipes-devtools/python/python3-httpcore2_2.16.0.bb
create mode 100644 meta-python/recipes-devtools/python/python3-truststore_0.10.4.bb
--
2.56.0
next reply other threads:[~2026-11-08 19:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 19:25 Thomas Roos [this message]
2026-11-08 19:25 ` [meta-python][PATCH 1/6] python3-pika: build the 1.4.4 release Thomas Roos
2026-11-08 19:25 ` [meta-python][PATCH 2/6] python3-pint: add missing runtime dependencies Thomas Roos
2026-11-08 19:25 ` [meta-python][PATCH 3/6] python3-haversine: keep working when numba fails to import Thomas Roos
2026-11-08 19:25 ` [meta-python][PATCH 4/6] python3-truststore: add recipe Thomas Roos
2026-11-08 19:25 ` [meta-python][PATCH 5/6] python3-httpcore2: " Thomas Roos
2026-11-08 19:25 ` [meta-python][PATCH 6/6] python3-httpx2: add missing runtime dependencies Thomas Roos
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=20261108192549.1082715-1-thomas@roosesweb.de \
--to=roosesweb@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=thomas@roosesweb.de \
/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.