-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: loc.__setitem__ over MultiIndex with slice key and step != 1 does strange things #8856
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
Comments
This was prob never tested properly. That said for loc/ix. You could step 'logically', meaning you step the 'levels', but not sure if that is useful. |
@immerrr able to get to this soon? otherwise I will bump to next version |
My schedule is flaky for ~2 more weeks, sorry. |
np...take your time |
I just looked at this.
|
changed title to reflect this and that .ix is deprecated. |
could add a test to confirm the .iloc behavior. |
Looks like both loc and iloc work consistently now
|
Here's how it looks like:
Regular setitem works fine:
I have some ideas about iloc refactoring that will fix that for iloc, but loc/ix will still be affected.
The text was updated successfully, but these errors were encountered: