-
Notifications
You must be signed in to change notification settings - Fork 77
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
Remove "edition" from GLOBAL_ATTRIBUTES_KEYS #234
Conversation
Codecov Report
@@ Coverage Diff @@
## master #234 +/- ##
===========================================
- Coverage 92.24% 54.59% -37.65%
===========================================
Files 25 25
Lines 1754 1740 -14
Branches 206 206
===========================================
- Hits 1618 950 -668
- Misses 112 774 +662
+ Partials 24 16 -8
Continue to review full report at Codecov.
|
@StephanSiemen , do you get any test failures when you run pytest? I get the same errors as are shown un the Ubuntu py3.8 tests on github. |
I don't really like just removing tests, and some of those were testing something that was not being tested elsewhere, so I put some substitute tests in place. These are not related to the failing tests, they are only in test_40_xarray_store.py |
My fear is that cfgrib is storing and using the edition so that it can be used when writing an xarray to GRIB. And it could be important.... that said, the functionality to write GRIB is broken anyway with modern xarray/pandas versions. |
@alexamici , what do you think about this PR, and is the GRIB edition important for writing xarrays back as GRIB (it seems to be)? |
@iainrussell if you want to save the same GRIB file as the input it is needed to keep the It is not strictly needed by xarray, but cfgrib probably assumes that it is present at save time. |
As identified in issue #232, the GRIB edition should not be an global attribute key.
This is a duplicate of #233, because more changes are necessary to not have tests fail.