-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
DataFrame.ix losing row ordering when index has duplicates #3561
Comments
thanks for the catch, this is a case that though worked, was using a set like indexer so the order was not guaranteeed - provided an opportunity to refactor a bit...PR coming soon |
Unique
Duplicate
@dalejung @y-p @wesm |
re:
yeah, that is inconsistent. |
I think for consistency sake it should be the same. To be honest, I don't have a use case for indexing a non-existent label or an iterable key that contains a duplicate. I came across the bug when a source file upstream had a duplicate row. Thanks for the quick patch. |
np...we have been fixing duplicate indicies lately (again not there is that much use for them), but they should work....will be merged soon |
The problem is that the resulting DataFrame keeps the ordering of the
df.index
and not therows
key. You'll notice that therows
key doesn't reference a duplicate value.The text was updated successfully, but these errors were encountered: