-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: Groupby NaT Handling #6992
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
nope, these should be handled like maybe add some tests for this explicity (and |
see also #5456 |
Thanks. I'm working on #3729 now (hopefully finish it soon), and will handle |
If group key contains
|
group key should not contain |
Understood the principle, and I think it is better to |
xref #9236
There seems to be an inconsistency in some GroupBy methods when
NaT
is included in the group key.GroupBy.groups
includesNaT
as a key.GroupBy.ngroups
doesn't countNaT
.GroupBy.__iter__
doesn't returnNaT
group.GroupBy.get_group
fails whenNaT
is specified.I understand
NaT
should be included in the group key according to other function's behaviour, such asdropna
. Is it OK to fix it to includeNaT
?The text was updated successfully, but these errors were encountered: