Skip to content

value counts NaT doesn't count as NaN #7423

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.

Sign up for GitHub

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

Jump to bottom
Closed
hayd opened this issue Jun 10, 2014 · 0 comments · Fixed by #7424
Closed

value counts NaT doesn't count as NaN #7423

hayd opened this issue Jun 10, 2014 · 0 comments · Fixed by #7424
Labels
Bug Datetime Datetime data dtype Timedelta Timedelta data type
Milestone
0.14.1

Comments

@hayd
Copy link
Contributor

hayd commented Jun 10, 2014

fix on the way.

dt = pd.to_datetime(['NaT', '2014-01-01'])
value_counts(dt)  # should have one entry

(Actually there is an issue with timedeltas too (you can't create an timedelta index.)
@hayd hayd added Bug labels Jun 10, 2014
hayd added a commit to hayd/pandas that referenced this issue Jun 11, 2014
@hayd
FIX value_counts should skip NaT pandas-dev#7423
458dc94
This was referenced Jun 11, 2014
Merged
Closed
@jreback jreback added this to the 0.14.1 milestone Jun 11, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Datetime Datetime data dtype Timedelta Timedelta data type
Projects
None yet
Milestone
0.14.1
Development

Successfully merging a pull request may close this issue.

FIX value_counts should skip NaT hayd/pandas
2 participants
@jreback @hayd