You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 4, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 4, 2024. It is now read-only.
Merge PySPConfigBlock back into pyutilib.misc.config #8
In an effort to simplify / standardize configuration / options in Pyomo, we should ensure that we only use a single configuration management system. The customizations / overrides in PySPConfigBlock and PySPConfigValue should be reviewed and, if appropriate, merged into pyutilib.misc.config. PySP should then directly use the pyutilib.misc.config system.
@jsiirola: There are still a few methods on PySPConfigBlock that add or change functionality from ConfigBlock. Two of those could be move off of the class and just be made helper functions that I use in PySP (or potentially elsewhere). However, there are three other methods that make some pretty fundamental differences in behavior. The following example should summarize what those differences are:
Activity
ghackebeil commentedon Apr 13, 2018
@jsiirola: There are still a few methods on
PySPConfigBlockthat add or change functionality fromConfigBlock. Two of those could be move off of the class and just be made helper functions that I use in PySP (or potentially elsewhere). However, there are three other methods that make some pretty fundamental differences in behavior. The following example should summarize what those differences are:ConfigDict: normalize all keys to not contain spaces
ConfigDict: defining `__delattr__()`
Do not set "_userData" flag on containers when adding contents