bug: upgrade pygrib version from 2.1.6 to 2.1.8#124
Merged
mackenzie-grimes-noaa merged 3 commits intomainfrom Feb 5, 2026
Merged
bug: upgrade pygrib version from 2.1.6 to 2.1.8#124mackenzie-grimes-noaa merged 3 commits intomainfrom
mackenzie-grimes-noaa merged 3 commits intomainfrom
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
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.
Linear Issue
IDSSE-1616
Changes
pygribPython library version from2.1.6to2.1.8. ChangelogExplanation
Only in the dev environment (not on my local
macosmachine), DAS was seeing constant errors when it attempted to read some GRIB variable with pygrib (see DAS shrink_grib code):The sole maintainer of pygrib has published a new minor version since we last attempted. Maybe there was some mysterious incompatibility with another library we were using that has since been fixed? Or moving from
2.1.4to2.1.6introduced the error?