Adding an option to ConfigBase.__call__ to preserve implicit values #45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary/Motivation:
When using ConfigBlocks for configuring complex objects (like solvers in Pyomo), it becomes convenient to create temporary ConfigBlocks for holding transient options. We do that by calling the ConfigBlock. The catch is that if the block permits implicit keys, then we will want to preserve those implicit keys.
This PR adds a new option to
__call__
to cause the copy to preserve all implicitly-defined keys.Changes proposed in this PR:
preserve_implicit
option toConfigBase.__call__()
Legal Acknowledgement
By contributing to this software project, I agree to the following terms and conditions for my contribution: