Conversation
jedi-base-env pulled in 12 python packages, so every environment built on it inherited python whether or not it needed it -- including the model interface environments jedi-mpas-env and jedi-fv3-env. Move 11 of them into a new jedi-python-env bundle, following the existing neptune-env / neptune-python-env split. py-pybind11 stays in jedi-base-env because core JEDI packages link its headers. jedi-mpas-env and jedi-fv3-env are left with no python dependency other than py-pybind11. The other eight jedi-base-env dependents (ai-env, ewok-env, gmao-swell-env, jedi-geos-env, jedi-neptune-env, jedi-ufs-env, jedi-um-env, soca-env) gain an explicit jedi-python-env dependency so their content is unchanged. jedi-python-env is added to the unified-dev and skylab-dev templates.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change moves scientific python dependencies out of the primary c++/fortran build path for some JEDI components.
Motivation: AI work often is picky about python requirements and can clash with our primary environment. Many jedi components can build with a minimal python environment.
Fixes: https://github.com/JCSDA-internal/jedi-bundle/issues/146
Fixes: #1888