Numpy 2.0 will have breaking changes

[purva-thakre]

Saw this on Twitter. This issue is a placeholder to read the migration guide for the breaking changes.

https://numpy.org/news/#numpy-20-release-date-june-16

[nathanshammah]

Numpy 2.0 has now been released! Curious about how bad it will be in terms of breaking changes for Mitiq...

[purva-thakre]

During last week's community call, we discussed waiting for the dependabot PR to upgrade to the latest release.

If we have a large number of errors, we also discussed pinning the numpy version to the latest compatible one while we worked on the fixes.

mitiq/requirements/requirements.txt

Line 1 in bf82e84

numpy>=1.22.0

We will probably have to wait until most of our dependencies use the latest version of numpy.

[purva-thakre]

As noted in vprusso/toqito#656 (comment), numpy changed the representation for scalar type in 2.0. These show up in the print outputs.

https://numpy.org/neps/nep-0051-scalar-representation.html

So, the scalar outputs for examples in the documentation are expected to fail for the same reason when we upgrade to the latest numpy release.

[natestemen]

news from today's cirq community call: the next cirq release will include support for numpy 2.0.