-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: df.nsmallest get wrong results when NaN in the sorting column #46656
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
Conversation
Should this pr be recorded in 1.4.3 whatsnew? I see your 1.4.3 tag (instead of 1.5) on this issue. @simonjayhawkins |
Yes, this should move to 1.4.3 |
thanks @GYHHAHA |
@meeseeksdev backport 1.4.x |
Could not push to auto-backport-of-pr-46656-on-1.4.x due to error, aborting. |
…n NaN in the sorting column
Could not push to auto-backport-of-pr-46656-on-1.4.x due to error, aborting. |
@meeseeksdev backport 1.4.x |
Could not push to auto-backport-of-pr-46656-on-1.4.x due to error, aborting. |
…he sorting column (#46748) Co-authored-by: Yuanhao Geng <[email protected]>
NaN
#46589doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.