-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
pd.concat on two (or more) series produces all-NaN dataframe #11058
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
see #10060 you are using Just use This is the correct usage
This is technically a bug, but really really frowned upon.
I prop won't ever get to this. This really requires creation of a new dtype to support these. I don't think its worth it nor is it useful in any way. I mark it as a bug in any event. |
the one thing I think might useful is a note in the doc-string for |
I think I will do that. |
This looks to work on master now. Could use a test
|
Thanks @timfeirg for reporting this issue. before closing this, we should add a test to prevent regressions. |
this is from a stackoverflow question here, you can download serialized object here and reproduce using python 2.7 and pandas 0.16.2.
I'm trying to concat two series with multiindex using
pd.concat([a, b], axis=1)
like so:I've checked the index type and many other stuff to make sure no obvious were made, I've read the docs to learn that concatenating and merging series and dataframes may introduce
NaN
, but I didn't find anything in the docs to explain this behavior.The text was updated successfully, but these errors were encountered: