-
Notifications
You must be signed in to change notification settings - Fork 494
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 > 1.26.4 #1104
Comments
@Mikeriess I don't think it would be a substantial effort. We pinned to numpy 1 due to
The imports would need to be fixed. Unless there's something I'm missing this is a trivial change. |
Got it. Have had some compatibility issues with outlines and the newest llama.cpp version due to this, so if this is a trivial change that is great news 👍 |
Is the latest llama.cpp incompatible with I'd like to ensure this is high priority if it breaks the latest llama.cpp. |
What behavior of the library made you think about the improvement?
This issue is just meant as a Q&A, as I couldnt find anything specifically on this.
The question is why there is a dependency on older versions of numpy? What is the limitation in the newer numpy versions? And how big of a job do you estimate it would be to support newer versions of numpy?
How would you like it to behave?
Numpy > 1.26.4
The text was updated successfully, but these errors were encountered: