-
Notifications
You must be signed in to change notification settings - Fork 43
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
Port test_grib_load_translations from iris #191
Port test_grib_load_translations from iris #191
Conversation
I definitely agree with this! |
} | ||
) | ||
# Add edition-dependent settings. | ||
self["edition"] = edition |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Arguably you could edit this... but I don't think we need to worry about that right now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The way this is written, it still suggests that you can control what you get depending on what edition you supply to _init_minimal_message
,when that's not quite true anymore. But you do assert the edition is 1 later on.
Overall I'm happy with this. I'll merge... |
Tests ported from
iris.tests.test_grib_load_translations
.Renamed and slightly simplified, as this (now) only tests the old GRIB-1 mechanisms.
A case could be made for combining this with the existing "sister" testcode
iris_grib.tests.unit.grib1_load_rules.test_grib1_convert
, and unifying the approaches.But for GRIB1 I think this is strictly not worth it.
Maybe when we port GRIB1 to the new "strict" loader code ?