Bump Numpy

[MIWdlB]

Feature details

Pinning numpy to <2.1 is now becoming restrictive. What's the issue that stops this from being <3?

Implementation

No response

How important would you say this feature is?

3: Very important! Blocking work.

Additional information

No response

[josh146]

Thanks for opening this issue @MIWdlB! Our team is looking into this now, but there might be a pathway for removing our NumPy pinning for certain workflows.

However, this becomes a bit more complicated if you are using JAX with PennyLane. Currently, are you using Catalyst and/or JAX for anything?

[CatalinaAlbornoz]

Hi @MIWdlB , I just wanted to give you an update on this.

We're evaluating options at the moment. We have PR #7039 open to try to unpin NumPy. Since this may not be a trivial change we may need to wait a bit before this gets merged into master. However you can follow the PR to see if we have any updates there.
Note that we do have it in our roadmap to support newer versions of NumPy, it may just take some time in case other things break with the change.

[MIWdlB]

Thanks for the update, I've had to remove penny lane from my own repos for the time being. I'll keep an eye on the PR and add it back in when the time comes.

If there's jobs along the way that I can help out on I'd be happy to ☺️

[CatalinaAlbornoz]

Oh that's unfortunate. Hopefully we'll be able to unpin it soon. We'll keep you updated and let you know if we can use your help! At the very least we can use your help flagging any issues once the change is done 😄