-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Don't create (or add option to not create) empty columns when unstacking #1181
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
Comments
@rkern looks like I fixed this one. Was actually much less trivial than I expected. Here's an example table that would have had lots of empty columns before:
Take it for a spin with your data set and let me know if you have any problems |
It doesn't look like it gives the correct (lexicographic) ordering of the columns when there are NA cells. When there is enough data for all cells to be "full", the right ordering is restored. |
I see. That is indeed annoying. So the issue is that prior to reshaping the data are lexicographically sorted:
But after reshaping, not so much. So I think the prudent thing is just to sort the columns before returning with |
OK it's a done deal |
I'm getting an error:
|
Doh, you're 32-bit. I'm in the midst of sorting out a bunch of int32/int64 issues (started last night), hopefully have the test suite passing on 32-bit within a few hours |
No rush. |
Jenkins is very unhappy |
Test suite passing on 32-bit platforms now. Let me know if you run into any problems |
Works for me. Thanks! |
from @rkern on the pydata mailing list:
to my response
The text was updated successfully, but these errors were encountered: