-
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
Minor fixes for Numpy 2 #1228
Minor fixes for Numpy 2 #1228
Conversation
Tests now failing with cyvcf2 code: |
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 thanks @timothymillar
The cyvcf2 fix is not ready yet so should we merge this now, along with a numpy<2 pin?
cyvcf2 and cbgen both have new releases for numpy 2 (the latest cbgen pins to numpy >= 2). But the tests against scikit-allel are still failing. Maybe time to add the scikit-allel test data and drop the dependency? |
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.
Good to merge now
Agreed, let's pin to numpy < 2 for now and push out a release? |
I wonder if we need the scikit-allel conversion still? We could deprecate Thoughts @jeromekelleher? |
I'm wondering the same, it may be best to just drop direct VCF support soon and be done with it. |
Fixes #1225
This only fixes a couple of small issues for Numpy 2 compatibility. However, many tests are still failing due to Cython-Numpy 2 compatibility issues. See brentp/cyvcf2#307.