From: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 15/18] python3-numpy: upgrade 2.5.3 -> 2.5.4
Date: Mon, 12 Oct 2026 15:20:02 +0200 [thread overview]
Message-ID: <20261012132005.23909-16-jaipaul.cheernam@est.tech> (raw)
In-Reply-To: <20261012132005.23909-1-jaipaul.cheernam@est.tech>
Release: https://github.com/numpy/numpy/releases/tag/v2.5.4
Contributors
============
A total of 9 people contributed to this release. People with a "+" by their
names contributed a patch for the first time.
Pull requests merged
====================
A total of 17 pull requests were merged for this release.
.. currentmodule:: numpy
=========================
NumPy 2.5.4 Release Notes
=========================
*Released on 2026-10-10.*
NumPy 2.5.4 is a patch release that fixes bugs discovered after the 2.5.3
release. Highlights are:
- Many typing fixes and improvements,
- A workaround for the MSVC 19.51 bug, see below.
This release supports Python versions 3.12-3.15.
Improvements
============
- ``numpy.linalg.svd`` and ``numpy.linalg.lstsq`` now raise for inputs
containing
infinities instead of returning garbage results.
- Fixed hangs in ``numpy.linalg.svd`` and ``numpy.linalg.lstsq`` for certain
inputs
containing infinities for recent versions of some LAPACK implementations.
- ``numpy.linalg.cond`` now handles non-finite inputs more consistently.
(`gh-32593 < >`__)
StringDType hashing with NaN sentinels
--------------------------------------
``StringDType`` instances with equivalent floating-point NaN sentinels now
have equal hashes. Previously, distinct NaN objects could produce equal
dtype instances with different hashes, causing dictionary lookups and set
deduplication to fail.
(`gh-32563 < >`__)
Changes
=======
``MaskedArray`` resets a fill_value that cannot be represented in a new dtype
-----------------------------------------------------------------------------
A fill_value copied from a source array is now reset to the default fill_value
for the new dtype when it cannot be represented in that dtype. Previously the
copied value could be stale: ufuncs that change dtype left the result holding a
fill_value typed for the old dtype, which raised a ``TypeError`` only when
something later validated it (such as ``.view()``), and a floating point
fill_value that overflows an integer dtype was kept as an out-of-range value
together with a ``RuntimeWarning``. Both now fall back to the default,
including when a masked array is passed to ``MaskedArray`` with a different
``dtype``. A fill_value given explicitly by the user is still validated and
raises as before. This can now raise a ``ComplexWarning`` if the fill_value is
complex and the new dtype is real.
(`gh-32508 < >`__)
(`gh-32562 < >`__)
Contributors
============
A total of 9 people contributed to this release. People with a "+" by their
names contributed a patch for the first time.
Pull requests merged
====================
A total of 17 pull requests were merged for this release.
Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
---
.../python/{python3-numpy_2.5.3.bb => python3-numpy_2.5.4.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-numpy_2.5.3.bb => python3-numpy_2.5.4.bb} (97%)
diff --git a/meta/recipes-devtools/python/python3-numpy_2.5.3.bb b/meta/recipes-devtools/python/python3-numpy_2.5.4.bb
similarity index 97%
rename from meta/recipes-devtools/python/python3-numpy_2.5.3.bb
rename to meta/recipes-devtools/python/python3-numpy_2.5.4.bb
index 338bdd2bbd..93aa356db1 100644
--- a/meta/recipes-devtools/python/python3-numpy_2.5.3.bb
+++ b/meta/recipes-devtools/python/python3-numpy_2.5.4.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] = "df2d5874ff183595a4ba404edd04f6bd9b5505c1d7708573f6a6c17489a67563"
+SRC_URI[sha256sum] = "9a94cf751c9ad8ebaa835bcd3d40dacf8534ad086b88c38029b65123c7999d2a"
GITHUB_BASE_URI = "https://github.com/numpy/numpy/releases"
UPSTREAM_CHECK_REGEX = "releases/tag/v?(?P<pver>\d+(\.\d+)+)$"
next prev parent reply other threads:[~2026-10-12 13:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 13:19 [PATCH 00/18] Upgrades on 12th October Jaipaul Cheernam
2026-10-12 13:19 ` [PATCH 01/18] pkgconf: upgrade 3.0.7 -> 3.0.8 Jaipaul Cheernam
2026-10-12 13:19 ` [PATCH 02/18] python3-uv-build: Upgrade 0.12.21 -> 0.13.0 Jaipaul Cheernam
2026-10-13 8:06 ` [OE-core] " Mathieu Dubois-Briand
2026-10-12 13:19 ` [PATCH 03/18] python3-pycparser: Upgrade 3.0 -> 3.11 Jaipaul Cheernam
2026-10-12 13:19 ` [PATCH 04/18] gstreamer1.0: upgrade 1.28.7 -> 1.28.8 Jaipaul Cheernam
2026-10-12 13:33 ` [OE-core] " Alexander Kanavin
2026-10-12 13:19 ` [PATCH 05/18] gstreamer1.0-python: " Jaipaul Cheernam
2026-10-12 13:19 ` [PATCH 06/18] gst-examples: " Jaipaul Cheernam
2026-10-12 13:19 ` [PATCH 07/18] gst-devtools: " Jaipaul Cheernam
2026-10-12 13:19 ` [PATCH 08/18] gstreamer1.0-libav: " Jaipaul Cheernam
2026-10-12 13:19 ` [PATCH 09/18] fastfloat: upgrade 8.3.0 -> 8.3.2 Jaipaul Cheernam
2026-10-12 13:19 ` [PATCH 10/18] python3-pygobject: upgrade 3.58.0 -> 3.58.1 Jaipaul Cheernam
2026-10-12 13:19 ` [PATCH 11/18] sqlite3: upgrade 3.53.4 -> 3.54.0 Jaipaul Cheernam
2026-10-12 13:19 ` [PATCH 12/18] python3-jsonpointer: upgrade 3.1.1 -> 3.2.1 Jaipaul Cheernam
2026-10-13 12:03 ` [OE-core] " Mathieu Dubois-Briand
2026-10-12 13:20 ` [PATCH 13/18] python3-beartype: upgrade 0.22.9 -> 0.23.0 Jaipaul Cheernam
2026-10-12 13:20 ` [PATCH 14/18] at-spi2-core: upgrade 2.62.0.1 -> 2.62.1 Jaipaul Cheernam
2026-10-12 13:20 ` Jaipaul Cheernam [this message]
2026-10-12 13:20 ` [PATCH 16/18] python3-pycryptodome,python3-pycryptodomex: upgrade 3.23.0 -> 3.24.1 Jaipaul Cheernam
2026-10-12 13:20 ` [PATCH 17/18] python3-hypothesis: upgrade 6.168.5 -> 6.169.0 Jaipaul Cheernam
2026-10-12 13:20 ` [PATCH 18/18] python3-beartype: Upgrade 0.23.0 -> 0.23.1 Jaipaul Cheernam
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=20261012132005.23909-16-jaipaul.cheernam@est.tech \
--to=jaipaul.cheernam@est.tech \
--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;
as well as URLs for NNTP newsgroup(s).