Pin numpy to <2.0 to fix zarr compatibility #41
Merged
+1
−1
Conversation
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
The zarr library uses np.PINF which was removed in NumPy 2.0. This constraint prevents pip installs from upgrading numpy beyond 1.x. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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.
Summary
>=1.23.0,<2.0in Docker environmentProblem
The zarr library uses
np.PINFwhich was removed in NumPy 2.0. Pip installs in the Dockerfile can upgrade numpy beyond the conda-pinned version, causing this error:This blocks all CI tests including PR #37 (H&E RGB thumbnail generation).
Fix
Changed from exact pin
numpy=1.23.0to rangenumpy>=1.23.0,<2.0to prevent any numpy 2.x installation while allowing patch updates.Testing
Once merged, Docker container will rebuild automatically. This unblocks testing for PR #37.
🤖 Generated with Claude Code