-
Notifications
You must be signed in to change notification settings - Fork 4
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
Make energy_system.nodes a dict #35
Conversation
The property energy_system.nodes now still contains dict_values. This should be compatible to the old list. Access by label is poosible using energy_system.node[key].
I discussed this with @gnn already at the dev meeting. If there are no objections within one week, I will merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most review items are only suggestions, except review item on property setter, which could cause errors!
The setter is problably unused, and I do not see a test for it. As I do not see a use case, I propose to delete it.
The test fails because reporting to Coveralls does not work. |
Erm... I actually had an objection and was trying to find the time to push alternative changes instead of raising an objection. That's why the one week objection period was actually important for me. |
Sorry, that I implied things that I did not mean to say. As there was an approval, I considered it to be okay. I would have waited for one week if there wasn't an feedback. Still, the changes are not in a published release, so please bring up your alternative. Update: As I learned in the chat, the idea is an API like nodel_labeled_sponk = energy_system.nodes.by_label["sponk"] |
Todo:
but we do have them. Another issue might be fixed with Move Node functionality from Entity to Node #30.
Node
s are organised in groupings. This can be done as a separate action.