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 @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!

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.

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.

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?

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...