Fix HDF4 reading utility using dtype classes instead of instances #891
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.
I think we were getting lucky in previous versions of numpy and xarray where a
dtype
class could be used relatively interchangeably with a dytpe instance. Now in numpy 1.17 this isn't magic anymore and we have to fix some of our usage. For example,np.float32
is a class (atype
) so things likenp.float32.itemsize
now return a property of a class not an instance.This PR makes it so the HDF4 utility class uses instances of dtypes to avoid some errors I was getting.
flake8 satpy