Just as a reminder or TODO (maybe for me during the next dev days):
From Pyomo-Version 5.4 on, which will be released within the next weeks, it will be possible to serialize (dump or deepcopy) pyomo models using Python 3 even if dict_keys are used for initialization. See here for the PR I induced concerning this problem with the forum post that illustrates the problem: https://github.com/Pyomo/pyomo/pull/305
Maybe we can connect this to the more centralised role of the energy system or a parent class with generic functionality that holds respective methods to serialize attributes like the model (in contrast to the current design). At least this seems to be one more intuitive architectural way that occurs on application level..
Just as a reminder or TODO (maybe for me during the next dev days):
From Pyomo-Version 5.4 on, which will be released within the next weeks, it will be possible to serialize (dump or deepcopy) pyomo models using Python 3 even if dict_keys are used for initialization. See here for the PR I induced concerning this problem with the forum post that illustrates the problem: https://github.com/Pyomo/pyomo/pull/305
Maybe we can connect this to the more centralised role of the energy system or a parent class with generic functionality that holds respective methods to serialize attributes like the model (in contrast to the current design). At least this seems to be one more intuitive architectural way that occurs on application level..