Remove ncl and its dependencies from main dependencies and add documentation how to install it #3853
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
On my local machine:
then, once the env is created and activated, if one needs NCL:
and timing for that is very reasonable:
So the user who needs NCL can just install it in the already created ESMValTool environment; of course, quite a few dependencies will be downgraded (and remember that even Python will be downgraded to 3.12 if the env is built with 3.13) but this is a lot more of an elegant and efficient solution for us, then to keep dragging NCL along with us!
The other two deps -
imagemagick
andnco
can be installed together with ncl in one call or separately, I am doing separately to see which deps modify each:and
both easy to have them installed!
Before you get started
Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.