Migrating to NumPy 2.0

[scarrazza]

At some point, we should also take into account migrating to NumPy 2.0, now that is out.

A much relevant improvement (to us) could be the following:
https://numpy.org/doc/stable/release/2.0.0-notes.html#array-api-compatible-functions-aliases
https://numpy.org/doc/stable/release/2.0.0-notes.html#array-api-compatible-functions-for-numpy-linalg
https://numpy.org/doc/stable/release/2.0.0-notes.html#array-api-standard-support-in-the-main-namespace

It was already documented for v1, and there are compatibility packages available
https://numpy.org/doc/stable/reference/array_api.html
but now it is available by default, and it should improve the compatibility with the other array frameworks (i.e. TensorFlow, PyTorch, JAX, CuPy, ...), since the Python API has been standardized (not all of them adopted it already, but they might do it).

Originally posted by @alecandido in #1395 (comment)

[glpatcern]

Ciao @MatteoRobbiati, @scarrazza, are you going to look into this migration any time soon?

I've got a request about this from the SWAN service at CERN, as they plan to move to numpy 2.0 and would potentially need to uninstall Qibo.

[MatteoRobbiati]

Ciao @MatteoRobbiati, @scarrazza, are you going to look into this migration any time soon?

I've got a request about this from the SWAN service at CERN, as they plan to move to numpy 2.0 and would potentially need to uninstall Qibo.

Ciao @glpatcern!
We have to solve some dependencies we still have in the tests with machine learning backends (mostly related to Keras and it's integration of Numpy 2.0). After this, we plan to support it indeed!

[glpatcern]

Hey @MatteoRobbiati, I guess this will take some time yet, right? I see there's also #1484 that is kind of related, but did not find any PR specifically addressing numpy 2.

At the moment, the SWAN team is ready to migrate to a new set of packages that support numpy 2 and python 3.12, and unless we (you) provide some context or roadmap, they may drop Qibo to give precedence to all the rest.

[alecandido]

Hey @MatteoRobbiati, I guess this will take some time yet, right? I see there's also #1484 that is kind of related, but did not find any PR specifically addressing numpy 2.

Hi @glpatcern. Indeed, the two are actually unrelated.

At the moment, the SWAN team is ready to migrate to a new set of packages that support numpy 2 and python 3.12, and unless we (you) provide some context or roadmap, they may drop Qibo to give precedence to all the rest.

Python 3.12 is fully supported (it came in #1231).

Concerning NumPy 2, I do not see any special dependency issue, nor any major problem. The API is in general pretty similar, so it is mostly (and most likely) a matter of testing, and fixing the minor differences that will arise in the process.
But no one has taken over the task, so I guess it is not happening immediately. Unless someone volunteers for this.

@MatteoRobbiati we may discuss the issue at the next meeting, to see if there is anyone willing to actually perform the migration.

[glpatcern]

Hi @alecandido, thanks for jumping in - good to learn that the TensorFlow dependency should not be an issue with going to NumPy 2 (with Python 3.12).

Have you had your meeting / did you assess what the migration would entail in terms of actual work?

[alecandido]

Have you had your meeting / did you assess what the migration would entail in terms of actual work?

I would say, no one volunteered. I will directly check with the most likely candidates (one of which is @MatteoRobbiati himself :P), but otherwise it will just stall...

[glpatcern]

Hey there, glad to see this work got completed earlier than one could expect!

Are you going to issue a new tag/release?

[alecandido]

We have a release schedule of about 1 month. I'm not sure when it will be next one. Usually, by the end of the month, but we're not really strict about it.

In any case, since this is relevant for some user, and the next upcoming technical update (i.e. py3.13 support #1484) as well, we could even consider anticipating it.

[renatomello]

I think the next release is scheduled for 10 days from now

…

On Tue, 11 Mar 2025 at 12:05, Alessandro Candido ***@***.***> wrote: We have a release schedule of about 1 month. I'm not sure when it will be next one. Usually, by the end of the month, but we're not really strict about it. In any case, since this is relevant for some user, and the next upcoming technical update (i.e. py3.13 support #1484 <#1484>) as well, we could even consider anticipating it. — Reply to this email directly, view it on GitHub <#1403 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABH5QVUYPF63X5HFIRTZXPD2T2KMPAVCNFSM6AAAAABLNIC73CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJTGA3TENJZHE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> [image: alecandido]*alecandido* left a comment (qiboteam/qibo#1403) <#1403 (comment)> We have a release schedule of about 1 month. I'm not sure when it will be next one. Usually, by the end of the month, but we're not really strict about it. In any case, since this is relevant for some user, and the next upcoming technical update (i.e. py3.13 support #1484 <#1484>) as well, we could even consider anticipating it. — Reply to this email directly, view it on GitHub <#1403 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABH5QVUYPF63X5HFIRTZXPD2T2KMPAVCNFSM6AAAAABLNIC73CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJTGA3TENJZHE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>