Updates to support numpy 2 - #366
Open
gelzinyte wants to merge 5 commits into
Open
Conversation
Contributor
|
Sounds good. We just updated to numpy 2 internally here as well. I'll review ASAP, but I'm not the one who owns the pypi. We can check the github automated actions - I suspect that if we tag with a new version it'll update on pypi automatically. |
Contributor
|
I own the pypi - but I do believe it should just be automatic if you tag the new version. I'll follow here if there are problems. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi!
I'd like to lift the hard
numpy<2cap, so that Workflow can be used with numpy2-only packages (e.g., fhi-vibes).Small updates:
xtb-pythonpackage (legacy; restricts to numpy<2) totbliteOnce this PR is merged, would it also be possible to issue a new PyPi release?