Bug#1025788: transition: numpy
> On Mon, 12 Dec 2022 at 23:27, Sandro Tosi <morph@debian.org> wrote:
> > thanks, numpy/1.23.5-2 has just been uploaded to unstable.
>
> \o/
In the meantime, since upstream released it, i've uploaded
numpy/1.24.0 to experimental and the autopkgtest results are
https://qa.debian.org/excuses.php?experimental=1&package=numpy
now, there's a lot of red in there but almost all of the errors come
in the format of
AttributeError: module 'numpy' has no attribute 'X'
with X being [float, int, bool, object, ...].
This is because, numpy upstream in 1.24.0, finally decided to expire
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases
some deprecations introduced in 1.20.0
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated
(released almost 2 years ago).
All of those are quite straightforward to fix, since often it's just
necessary to stop importing them from numpy and use the python native
types.
There are handful more errors in the form of:
* ValueError: setting an array element with a sequence. The
requested array has an inhomogeneous shape after 1 dimensions. The
detected shape was (2,) + inhomogeneous part.
* Too many indices for array: array is 0-dimensional, but 1 were indexed
which will need to be looked at in more details, likely by individual
projects upstream.
This additional transition seems to be comfortably in the reach for
Bullseye and will place us in a better position to get support from
upstream. I also anticipate that a few more patch releases (fixing
bugs etc) for the 1.24.x series will be published before Bullseye is
released and we would like to update numpy to them in Debian if
reasonable.
Please let me know if i can proceed with a numpy upload to unstable.
Regards,
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi
Reply to: