-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
concat() on Sparse dataframe returns strange results #12174
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
dupe of #10536 when making a report, ideally would have a simple copy-pastable example as well as |
Hi, I don't understand, the issue #10536 says that :
More over,
|
well, then pls show an example |
This is a pretty long example, sorry about it :
|
its the same issue as I pointed |
added to the master issue. Sparse have not gotten a lot of TLC; need someone to step up and give them some :) |
Yes #10627 is certainly root cause |
In case this ever helps someone, here is my favorite workaround for fixing semi-sparse dataframes:
|
@yonatanp not sure what you are showing here. This issue was fixed in 0.18.1 |
I still have this issue, when using pd.concat(..., axis=1) on SparseDataFrames with the same fill value:
|
I open a stackoverflow question here :
http://stackoverflow.com/questions/35083277/pandas-concat-on-sparse-dataframes-a-mystery
And someone ask me to open an issue on Github.
To summarise, I don't really understand what's going on after a concat of 2 sparse data frame...
After such concat, df.density or df.memory_usage, for example, will throw an error.
Moreover, the basic structure of the sparse result seems strange...
I'm sorry that the bug is not defined better.
The text was updated successfully, but these errors were encountered: