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

numpy 2.0 compatibility #218

Closed
effigies opened this issue Jun 7, 2024 · 9 comments · Fixed by #221
Closed

numpy 2.0 compatibility #218

effigies opened this issue Jun 7, 2024 · 9 comments · Fixed by #221

Comments

@effigies
Copy link
Member

effigies commented Jun 7, 2024

conda-forge/nitime-feedstock#32 indicates (unsurprisingly) that there are numpy 2.0 compatibilities.

With numpy 2.0 in RC phase, it's probably time to try to fix these.

I don't have the time at the moment, unfortunately.

@arokem
Copy link
Member

arokem commented Jun 7, 2024 via email

@effigies
Copy link
Member Author

effigies commented Jun 7, 2024

That sounds like a good idea.

@arokem
Copy link
Member

arokem commented Jun 12, 2024

Is this resolved by #217 ?

@larsoner
Copy link
Collaborator

Oh I guess not. Wheels are built against 2.0 but probably not tested against 2.0 actually 🤦

For example there are still np.sctypes in the code which no longer exists. I can open a quick PR to at least have one CI run with NumPy 2.0rc2 if that would help

@effigies
Copy link
Member Author

effigies commented Jun 12, 2024

#217 also didn't resolve #219 (edit: fixed issue number). I think we can add the nitime test suite to the cibuildwheel post-build step, to avoid adding a new entry/dimension to the regular test matrix.

https://cibuildwheel.pypa.io/en/stable/options/#test-command

@larsoner
Copy link
Collaborator

I think we can add the nitime test suite to the cibuildwheel post-build step, to avoid adding a new entry/dimension to the regular test matrix.

Good call, I'll add this to #221. It's not 100% trivial, though, because 2.0 hasn't officially landed yet. I could separate the tool.cibuildwheel.test-requires to use different NumPy versions for testing different wheels if that would help. This is similar to how in #221 I just install NumPy 2.1.dev for the Python 3.11 run only.

@effigies
Copy link
Member Author

Is aarch only supported by numpy 2? I think they've had wheels for ages, and we should be able to test against numpy 1.

@larsoner
Copy link
Collaborator

Is aarch only supported by numpy 2? I think they've had wheels for ages, and we should be able to test against numpy 1.

No it's supported on 1.26 for example as well. I was just saying "enabling tests during wheel build" won't trivially solve the "need to test against NumPy 2.0" problem. But agreed that enabling tests during wheel building would help with #219 either way.

@effigies
Copy link
Member Author

Sorry, yeah. I was just going where the conversation was, and looking at the issue title, I see why you assumed numpy 2.0.

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 a pull request may close this issue.

3 participants