Skip to content

Reorganize JEDI meta-module enviornments to separate advanced python dependencies. - #2134

Draft
eap wants to merge 4 commits into
JCSDA:developfrom
eap:feature/python-jedi-reorg
Draft

eap wants to merge 4 commits into
JCSDA:developfrom
eap:feature/python-jedi-reorg

Conversation

@eap

@eap eap commented Sep 24, 2026 •

Copy link
Copy Markdown
Collaborator

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

eap added 4 commits September 24, 2026 21:59
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.
@eap eap changed the title draft: reorganize jedi enviornments to separate out advanced python dependencies. Reorganize JEDI meta-module enviornments to separate advanced python dependencies. Sep 29, 2026
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

Successfully merging this pull request may close these issues.

[INSTALL/QUESTION]: Add support for zarr

1 participant