Skip to content
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

pandas (and dask) cannot yet handle NAs during groupby #171

Open
jangorecki opened this issue Dec 14, 2020 · 1 comment
Open

pandas (and dask) cannot yet handle NAs during groupby #171

jangorecki opened this issue Dec 14, 2020 · 1 comment

Comments

@jangorecki
Copy link
Contributor

jangorecki commented Dec 14, 2020

dropna argument has been added to pandas groupby in 0.24.0 but till now it does not yet support categorical fields. It silently produces incorrect answer.
Data case having NAs (i.e. G1_1e7_1e2_5_0) will have to be escape for now for those two solutions.
We will enable it once pandas-dev/pandas#36327 will be resolved.

@jangorecki
Copy link
Contributor Author

In case of dask, it wasn't yet implemented at all, not just for categorical type. dask/dask#6986

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant