-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
BUG: Fix sort_values bug that creates unprintable object #39464
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
Hello @zitorelova! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found: There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2021-02-03 14:54:59 UTC |
e330b64
to
4f0d461
Compare
needs a test |
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.
pls add a test and a whatsnew note in reshaping bug fixes for 1.3
n_rows = 4 | ||
|
||
random_state = np.random.RandomState(seed=42) | ||
test_dict = { |
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.
can you just use a fixed input, so we can directly use assert_frame_equal on the results and compare it exactly.
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.
I've simplified the test so that it only uses fixed inputs.
6f2fdb3
to
47f970a
Compare
precommit is failing |
precommit is passing now |
Seems to be a |
thanks @zitorelova |
The problem occurs when sorting on columns and the
ignore_index
parameter is set toTrue
.sort_values
tries to refit the index after the columns have been sorted resulting in a corrupted dataframe.