You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Questionable behaviour in MaskedArray.__eq__ on flexible arrays #8589
In the commit pointed too, in another similar change, there is a comment: "# In case we have nested fields..."
So, at least that gives a hint why this was introduced. Indeed, one of the test cases shows that it is at least one thing the ValueError is meant to catch:
Just checking now: my try/except/else indeed throws the same errors as found in #8584, and those disappear when I (correctly) set axis=-1. PR to come soon.
Activity
charris commentedon Feb 9, 2017
@mhvk @ahaldane Thoughts.
mhvk commentedon Feb 9, 2017
In the commit pointed too, in another similar change, there is a comment: "# In case we have nested fields..."
So, at least that gives a hint why this was introduced. Indeed, one of the test cases shows that it is at least one thing the
ValueErroris meant to catch:In principle, I guess one should really write
But where does the indexing go wrong? I must say having a default of
axis=1seems very odd; surely, this should beaxis=-1?!?!mhvk commentedon Feb 9, 2017
Just checking now: my
try/except/elseindeed throws the same errors as found in #8584, and those disappear when I (correctly) setaxis=-1. PR to come soon.eric-wieser commentedon Feb 9, 2017
Does this mean there is a bug with masked 2D record arrays?
mhvk commentedon Feb 9, 2017
Yes. What a code... Anyway, fix almost done.
mhvk commentedon Feb 9, 2017
See #8590 for a fix.
eric-wieser commentedon Apr 4, 2017
@mhvk: We can close this as of #8590, right?
mhvk commentedon Apr 5, 2017
Yes!