Move buildnml into a package in cime_config #62
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This new directory will be a python package that can be imported by the various cime scripts
buildnml is now defined in the __init__.py file
billsacks
reviewed
Dec 15, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of changes:
Per ESMCI/cime#4076, we want to follow a convention where
.pyfiles are meant to be imported and python files without the.pyextension are meant to be run as scripts from the command line. I'm using POP as a test-bed for CIME updates to verify this sort of split is feasible in CESM.Testing:
Currently just testing by verifying the POP namelist is not changing, but I'll do more extensive tests before opening this up to be merged.
User interface (namelist or namelist defaults) changes? None