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
Weird behavior of structured_to_unstructured on non-trivial dtypes #13333
A lot of this behavior looks undesirable to me. @ahaldane, which cases were actually intended to be supported? Rather than locking ourselve into some of these weird constucts, we might want to raise an error for anything non-trivial.
Activity
ahaldane commentedon Apr 22, 2019
Good catches, I don't think the "weird" cases were intended.
Looks like you already have the fix for the one-field bug in #13332.
For the subarray bug, there is evidently some wrong recursion code. The bug contradicts the docstring for
_get_fields_and_offsets.mattip commentedon May 16, 2019
Can we close this? #13332 and #13334 were merged
eric-wieser commentedon May 16, 2019
No, the other weird cases still apply
charris commentedon Aug 20, 2019
Pushed off to 1.17.2.
ahaldane commentedon Aug 20, 2019
Thanks for the ping, I'd forgotten this was hanging.
I've got a fix for the cases above, will make PR soon.
MAINT: fix behavior of structured_to_unstructured on non-trivial dtypes
MAINT: fix behavior of structured_to_unstructured on non-trivial dtypes
MAINT: fix behavior of structured_to_unstructured on non-trivial dtypes