Adding constraint to zarr during install#113
Closed
fmalatino wants to merge 0 commit intoNOAA-GFDL:developfrom
Closed
Adding constraint to zarr during install#113fmalatino wants to merge 0 commit intoNOAA-GFDL:developfrom
zarr during install#113fmalatino wants to merge 0 commit intoNOAA-GFDL:developfrom
Conversation
fmalatino
force-pushed
the
update/submodules
branch
from
06b306e to
6c0ed5a
Compare
fmalatino
force-pushed
the
update/submodules
branch
from
ddc647f to
6c0ed5a
Compare
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
1 participant
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.
Description
This PR sets a constraint for the requirement of the
zarrpackage to< 3insetup.py. This was per the recommendation of the NASA team who found a break in the API whenzarr > 3.🚧
Can be merged in after PR 114
How Has This Been Tested?
Tested using the current CI workflow
Checklist: