We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
reported by Joris C:
Not sure whether it's due to a change in the job manager, or whether it was there already, but I'm getting a warning on the line here: https://github.com/Open-EO/openeo-python-client/blob/master/openeo/extra/job_management.py#L650 SettingWithCopyWarning: A value is trying to be set on a copy of a slice from a DataFrame. Try using .loc[row_indexer,col_indexer] = value instead See the caveats in the documentation: https://pandas.pydata.org/pandas-docs/stable/user_guide/indexing.html#returning-a-view-versus-a-copy active.loc[i, "running_start_time"] = rfc3339.utcnow()
The text was updated successfully, but these errors were encountered:
I already looked into this issue, but I could not yet reproduce this warning from using the job manager.
I can reproduce it with some simple pandas usage like
df = pandas.DataFrame({"foo": range(10)}) active = df[df.foo % 3 == 0] active.loc[3, "foo"] = 666
but I would need a more practical usage example of the job manager that triggers this
Sorry, something went wrong.
MultiBackendJobManager: fix another SettingWithCopyWarning related bug
5b1e8fa
seems like pandas is handy to build foot guns maybe related to #641
No branches or pull requests
reported by Joris C:
The text was updated successfully, but these errors were encountered: