-
Notifications
You must be signed in to change notification settings - Fork 5
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
Numpy2 fix #199
Numpy2 fix #199
Conversation
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.
Looks good to me!
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.
LGTM
Merging with positive review from @jons-pf (github complains because your other account is the official contributor to spec, sorry for the doubled requests Jonathan, and thanks for the review!) |
My only recommendation is to convert the versioning scheme to an automatic one based on Git hashes such as setuptools_scm. |
Numpy 2.0 breaks the binary interface to compiled code. And it is what is installed with 'pip install numpy'. Binaries compiled with numpy<2.0 cannot run with 2.0.
Therefore we need to upgrade the repo and binaries so it is installed with numpy2.0, but leaves the system numpy intact.
This PR does that, and is part of the numpy2.0 migration of simsopt (hiddenSymmetries/simsopt#427)
A speedy review would be appreciated, the changes are minor. The specific branch of f90wrap is also awaiting PR approval on upstream branch, so we might soon switch away from needing our private branch (jameskermode/f90wrap#194).
The edits to src/hesian.f90 are because the new f90wrap includes more meta-info in function docstrings, and LaTeX in python strings gives unexpected escape caracters.
Will merge with two approving reviews, tests are passing.