-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: unnecessary FutureWarning in sort_values #45668
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
jbrockmendel
commented
Jan 28, 2022
- closes BUG: passing a SparseArray to pd.Index - overly eager FutureWarning #45618
- tests added / passed
- Ensure all linting tests pass, see here for how to run them
- whatsnew entry
hmm failing tests though |
yah places where we are testing for futurewarning and no longer getting them. will update. |
updated + greenishx |
doc/source/whatsnew/v1.4.1.rst
Outdated
@@ -28,6 +28,7 @@ Fixed regressions | |||
Bug fixes | |||
~~~~~~~~~ | |||
- Fixed segfault in :meth:``DataFrame.to_json`` when dumping tz-aware datetimes in Python 3.10 (:issue:`42130`) | |||
- Stopped emitting unnecessary ``FutureWarning`` in :meth:`DataFrame.sort_values` with sparse columns (:issue:`45618``) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Extra backtick at the end of the issue number
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch, will update
@meeseeksdev backport 1.4.x |
Something went wrong ... Please have a look at my logs. |
…5727) Co-authored-by: jbrockmendel <[email protected]>