From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] python3-numpy: upgrade 2.5.2 -> 2.5.3
Date: Wed, 9 Sep 2026 09:10:20 +0100 [thread overview]
Message-ID: <20260909081020.2238149-2-richard.purdie@linuxfoundation.org> (raw)
In-Reply-To: <20260909081020.2238149-1-richard.purdie@linuxfoundation.org>
The NumPy 2.5.3 is a patch release that fixes bugs discovered after the 2.5.2
release. Apart from the usual bug and maintenance work, there are a number of
StringDType related fixes for problems discovered during the ongoing string
work in the main branch.
This release supports Python versions 3.12-3.15
Changes
=======
* Casting a fixed-width byte string array (``np.bytes_``) to ``StringDType``
now raises ``TypeError`` when the bytes are not valid UTF-8. Previously the
invalid bytes were stored as-is and later caused undefined behavior in
string operations.
(`gh-32296 <https://github.com/numpy/numpy/pull/32296>`__)
* ``MaskedArray._fill_value`` would become stale when ufuncs that change dtype
left the result holding a fill_value typed for the old dtype. The mismatch
was silent until something later called ``_check_fill_value``, such as
``.view()``, and then a ``TypeError`` would be raised. Now, when the copied
fill_value is no longer valid for the new dtype, fall back to the
default fill_value for that dtype instead of propagating the stale value.
This may raise a ``ComplexWarning`` if the fill_value is complex and the
new dtype is real.
(`gh-32423 <https://github.com/numpy/numpy/pull/32423>`__)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
.../python/{python3-numpy_2.5.2.bb => python3-numpy_2.5.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-numpy_2.5.2.bb => python3-numpy_2.5.3.bb} (97%)
diff --git a/meta/recipes-devtools/python/python3-numpy_2.5.2.bb b/meta/recipes-devtools/python/python3-numpy_2.5.3.bb
similarity index 97%
rename from meta/recipes-devtools/python/python3-numpy_2.5.2.bb
rename to meta/recipes-devtools/python/python3-numpy_2.5.3.bb
index 44062046810..c88b0bf1a29 100644
--- a/meta/recipes-devtools/python/python3-numpy_2.5.2.bb
+++ b/meta/recipes-devtools/python/python3-numpy_2.5.3.bb
@@ -10,7 +10,7 @@ SRCNAME = "numpy"
SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/${SRCNAME}-${PV}.tar.gz \
file://run-ptest \
"
-SRC_URI[sha256sum] = "d482d171c406ae88c5b19cad3b6a1c4c5209f886ab74bc44c2c865c23f52d860"
+SRC_URI[sha256sum] = "df2d5874ff183595a4ba404edd04f6bd9b5505c1d7708573f6a6c17489a67563"
GITHUB_BASE_URI = "https://github.com/numpy/numpy/releases"
UPSTREAM_CHECK_REGEX = "releases/tag/v?(?P<pver>\d+(\.\d+)+)$"
prev parent reply other threads:[~2026-09-09 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 8:10 [PATCH 1/2] python3-git: upgrade 3.1.61 -> 3.1.62 Richard Purdie
2026-09-09 8:10 ` Richard Purdie [this message]
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=20260909081020.2238149-2-richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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