-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
BUG: NaN level values in stack() and unstack() #9406
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
Labels
Milestone
Comments
Thanks, @behzadnouri. Sorry I missed those. Unless I'm missing something, the problem with
|
will mark this as a bug. clearly an edge case, but @behzadnouri fixed this for unstack so.... |
This looks fixed on master. Could use a test
|
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As described in #9023 (comment), the way
DataFrame.stack()
andDataFrame.unstack()
treatNaN
indices is rather odd/inconsistent. Despite passingtest_unstack_nan_index()
intest_frame.py
, I observe the following (this is from 0.15.2, but I think it's unchanged in the current master for 0.16.0):The text was updated successfully, but these errors were encountered: