Skip to content
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

Support parser interpolation? #131

Open
tclune opened this issue Oct 10, 2019 · 0 comments
Open

Support parser interpolation? #131

tclune opened this issue Oct 10, 2019 · 0 comments

Comments

@tclune
Copy link
Collaborator

tclune commented Oct 10, 2019

Summary of Issue:

The strict format checking currently prevents us from exploiting some of the power of Python configs. In particular it would be useful to have a default section where additional variables could be defined and then used with interpolation in subsequent sections.

I can probably implement as it is mostly loosening some of the protections, but want to gauge the interest before I try.

Expected behavior and actual behavior:

[DEFAULT]
BASE: [email protected]:GEOS-ESM   # ME complains that "BASE" is not a known key.

[GMAO_Shared]
repo_url = ${DEFAULT:BASE}/GMAO_Shared.git
local_path = ./src/Shared/@GMAO_Shared
tag = v1.0.5
sparse = ../../../config/GMAO_Shared.sparse

[GEOSgcm_App]
repo_url = ${DEFAULT:BASE}/GEOSgcm_App.git
local_path = ./src/Applications/@GEOSgcm_App
tag = v1.0.3

should allow us to just edit the BASE line at the top to reflect

Steps to reproduce the problem (should include model description file(s) or link to public repository):

N/A

What is the changeset ID of the code, and the machine you are using:

N/A

have you modified the code? If so, it must be committed and available for testing:

N/A

Screen output or log file showing the error message and context:

N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant