Skip to content

build: set numpy>=1.26.4 #301

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.

Sign up for GitHub

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

Merged
e06084 merged 1 commit into from
Dec 18, 2025
Merged

build: set numpy>=1.26.4 #301

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion requirements/runtime.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Pillow>=9.4.0
prettytable
pyahocorasick
nltk
numpy==1.26.4
numpy>=1.26.4
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Dec 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

While loosening the version constraint for numpy provides flexibility, using an open-ended >= is risky. The upcoming NumPy 2.0 release contains significant breaking API changes that will likely break this project. It's a safer practice to specify an upper bound to prevent your project from automatically installing incompatible major versions. This will ensure stability while still allowing for patch and minor updates.

numpy>=1.26.4, <2.0

pydantic
requests
textstat
Expand Down