Move NEPTUNE Python dependencies into its their own package neptune-python-env, remove legacy environment variables for NEPTUNE #1343
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
This PR moves the full NEPTUNE Python dependencies into their own package
neptune-python-dev
. Only the basic dependencies onf90nml
andpython-dateutil
remain inneptune-env
(needed by NUOPC).The
espc
variant is turned off by default inneptune-env
, but theneptune-dev
template enables it. Likewise, thexnrl
variant is turned off by default inneptune-python-env
, but theneptune-dev
template enables it.Several legacy environment variables for
hdf5
,libyaml
,p4est
are removed fromconfigs/common/modules_*.yaml
.Testing
gcc
in neptune_atmosgcc
in dsapigcc
in ioapiApplications affected
NEPTUNE, JEDI-NEPTUNE
Systems affected
None
Dependencies
n/a
Issue(s) addressed
Working towards #1342 (for NEPTUNE only)
Checklist
All dependency PRs/issues have been resolved and this PR can be merged.