Uh oh!
There was an error while loading. Please reload this page.
new methods to optionally re-enable old numpy array type behaviour (issue #809) - #816
Conversation
David Hassell seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
Looks good, thanks @davidhassell. Just needs a Changelog entry. |
akrherz
commented
Jul 16, 2018
Just a comment from the peanut gallery here and I know API design is hard, but the name Just my unqualified two cents here. |
davidhassell
commented
Jul 16, 2018
Sounds good. |
davidhassell
commented
Jul 16, 2018
jswhit
commented
Jul 16, 2018
Not quite clear on what |
as per the discussion in issue #808, please go ahead and change # issue #785: always return masked array, if no values masked# set mask=False.data=ma.masked_array(data,mask=False,fill_value=fill_value)to # issue #785: always return masked array by default, if no values maskeddata=ma.masked_array(data) |
davidhassell
commented
Jul 16, 2018
Yes - The logic needs reversing when we rename to |
jswhit
commented
Jul 17, 2018
Looks like tst_multifile.py is failing somewhere in cftime. Restoring the 'mask=False' fixes it. |
davidhassell
commented
Jul 18, 2018
I suggest, then, that we restore |
No description provided.