Skip to content

BUG: Index.min and max doesnt handle nan and NaT properly #7279

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

Merged
merged 1 commit into from
May 30, 2014

Conversation

sinhrks
Copy link
Member

@sinhrks sinhrks commented May 29, 2014

Closes #7261.

@jreback jreback added this to the 0.14.1 milestone May 29, 2014
jreback added a commit that referenced this pull request May 30, 2014
BUG: Index.min and max doesnt handle nan and NaT properly
@jreback jreback merged commit 7b59ebf into pandas-dev:master May 30, 2014
@jreback
Copy link
Contributor

jreback commented May 30, 2014

thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Dtype Conversions Unexpected or buggy dtype conversions Missing-data np.nan, pd.NaT, pd.NA, dropna, isnull, interpolate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

API: Should Index.min and max use nanmin and nanmax?
2 participants