Skip to content
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

Support numpy 2.0 #476

Merged
merged 5 commits into from
Aug 16, 2024
Merged

Support numpy 2.0 #476

merged 5 commits into from
Aug 16, 2024

Conversation

akaszynski
Copy link
Collaborator

Add support for numpy 2.0 by building with numpy 2.0 and requiring at least numpy 2.0.

Users who've not made the switch can still work with the previous release which will be automatically resolved by pip (as it is, for example, with matplotlib).

Copy link
Contributor

@germa89 germa89 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @akaszynski ! Glad to see you here again! It looks good to me!

@akaszynski akaszynski enabled auto-merge (squash) August 16, 2024 19:01
@akaszynski akaszynski merged commit 7416367 into main Aug 16, 2024
16 checks passed
@akaszynski akaszynski deleted the fix/support-numpy-2.0 branch August 16, 2024 19:05
Comment on lines 366 to 368
cdef np.ndarray ndarray
ndarray = np.array(array_wrapper, copy=False)
ndarray = np.array(array_wrapper)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couldn't we resolve this based on the numpy version used? Preventing users from using numpy 1.x only for this change seems a bit excessive IMO. Many libraries are still struggling with the switch to numpy 2.X so this might be an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants