-
Notifications
You must be signed in to change notification settings - Fork 32
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
Test against numpy 2.0 #166
Conversation
cfe0b31
to
371b43c
Compare
0b9597e
to
6c8c8d6
Compare
@@ -45,7 +45,7 @@ | |||
mfuncnames = [mf.name for mf in mfuncs] | |||
|
|||
|
|||
@pytest.fixture(params=[-360, 0, 360]) | |||
@pytest.fixture(params=[-360., 0., 360.]) |
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.
The hardest part was setting up the np2.0 test! This was the only failure we had due to https://numpy.org/devdocs/numpy_2_0_migration_guide.html#changes-to-numpy-data-type-promotion
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.
@efiring this is the only code change in this PR. Everything else is to be able to set a testing matrix with numpy 2.0. This PR also adds a test for the code generation step that serves both as test and developer breadcrumbs in case we need to do that locally.
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.
Thank you.
There are some significant changes in the next release. Hopefully it won't be too hard to port the code to it.