-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Allow interoperability with numpy 2.x #3064
Conversation
This works in numpy 1.26.4 at least. There are warnings about accessing numpy internals, so we'll see what happens next.
This was removed from top-level namespace in numpy 2.0, but all versions allow np.exceptions.AxisError.
ak_full_like.py feels like it could use a touch of refactoring.
This should work (by not triggering) for numpy 1.x again.
I'll review it when it's done. (We use the "request review" button as a way to get my attention to review it when it's time to decide if it can be merged as-is or needs changes. The "ready for review" button doesn't send me an email, but "request review" does.) |
…an a simple look-up)
…cored) interfaces
…an a simple look-up)
…an a simple look-up)
…ght by NumPy 2.0, and not by 1.x
@ManasviGoyal, (real?) errors in these two kernel tests are being caught by NumPy 2.0, and not by 1.x: 2bcb015 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved! We pair-programmed on Zoom.
Great to see this! I'm making a compatibility overview for numpy 2.0; can I ask what version of Awkward Array this will land in? |
Awkward 2.6.3, which is waiting on one more fix from #3068. I hope it will be done today. |
Awesome, thanks @jpivarski. |
We would like to allow awkward to work correctly with numpy 2.x.