-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
SparseSeries.dropna() returns "NaN"s for values #730
Comments
Need to have a special implementation of |
My expectation would be a regular dense Series (consisting of only the indexes with values), but I have limited experience in these things. If someone wanted a SparseSeries returned, why would they be running |
Suppose that you had |
…se Series in case of NA fill value, GH #730
I fixed this up in git master. Will be part of 0.7.0 final |
Great, thanks for that! What did you end up deciding to do about the return On Sat, Feb 4, 2012 at 11:07 PM, Wes McKinney <
|
When the fill_value is NaN it will return a dense Series. When it's non-NA it will return another SparseSeries. Somewhat "impure" but I think that will be the most useful behavior |
pypandoc deprecated the old function and does not render correctly with RST anymore
A SparseSeries object I have called ".dropna()" on will output the indexes which are not NaN (which is correct), but shows "NaN" in the value column.
If I run SparseSeries.to_dense().dropna() I get the expected output ie. non-NaN indexes and their values.
The text was updated successfully, but these errors were encountered: