-
Notifications
You must be signed in to change notification settings - Fork 450
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
FutureWarning #212
FutureWarning #212
Conversation
…tion is deprecated
…ration is deprecated
looks good. Did you have a |
Interesting. Here's the referring issue pandas-dev/pandas#36758. Do not merge yet, as there are many more cases of set operations on |
I can, but it's hard to detect all of them. Suggestions on how I can find all of them? |
Thanks @martacki. Only found a couple more in the unit commitment section. |
* fix clustering of offwind-ac and offwind-dc in sites option * add release nodes * attach renewable assets by location (lat and lon) from OPSD register to network * adapt default config to changes * undo changes from a differen PR in cluster_network.py * undo changes from a different PR, add release notes for this PR * correct release notes * add comments for relevant settings in add_electricity.py * adjust configtable for electricity to OPSD renewable option and add estimate_renewable_capacities_from_capacitiy_stats * reset cluster_network to HEAD * add_electricity: Capacity is float * config: add GB to OPSD_VRE_countries * review and modify implementation * update release notes * Update envs/environment.yaml Co-authored-by: Fabian Neumann <fabian.neumann@outlook.de> Co-authored-by: martha.frysztacki <eb5194@iai-esm003.iai.kit.edu> Co-authored-by: eb5194 <martha.frysztacki@kit.edu> Co-authored-by: Fabian Neumann <fabian.neumann@outlook.de>
The following FutureWarning affects
io.py
andlinopf.py
:Index.__or__ operating as a set operation is deprecated, in the future this will be a logical operation matching Series.__or__. Use index.union(other) instead
&Index.__and__ operating as a set operation is deprecated, in the future this will be a logical operation matching Series.__and__. Use index.intersection(other) instead
As suggested,
.union()
instead of a logicalor
/|
and.intersection()
instead od a logicaland
/&
should avert the problemIf you find other scripts that print the same Warning, comment or include them into this PR? Thanks