-
Notifications
You must be signed in to change notification settings - Fork 654
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
using .iloc to assign new value #1556
Comments
Thanks @ndy-cd, we prefer the new issue since the old one was resolved. This issue is slightly different because of the assignment. So what is happening is that the Assignment with import modin.pandas as pd #dask
test = pd.DataFrame({'first': range(10)})
test.loc[0, 'first'] = 500 # 0 is the Index value of the 0th row
#or test.iloc[[0, 1, 2], 'first'] = 500
print(test) If you prefer to use import modin.pandas as pd #dask
test = pd.DataFrame({'first': range(10)})
test.iloc[0, 0] = 500 # 0 is the column and row number
#or test.iloc[[0, 1, 2], 0] = 500
print(test) We have the machinery in place to support this, but it looks like something got lost with the double indexing. Thanks for the detailed report! We will get this fixed. |
Thank you very much for detailed answer! It seems to be a same problem with using .replace() |
Thanks @ndy-cd, that is expected behavior. Pandas has many ways to do the same thing as you probably know, we have one internal way to do things so that we can better optimize these fundamental operations. |
…`iloc` Signed-off-by: Devin Petersohn <[email protected]>
…`iloc` (modin-project#1788) Signed-off-by: Devin Petersohn <[email protected]>
System information
Problem:
When trying to use .iloc to assign a new value there are no changes taking place.
I already left a comment on the issue #147 but it's already closed and I wasn't sure that you can see it.
Code to reproduce:
The text was updated successfully, but these errors were encountered: