Don't remove esmf
from conda environment
#372
Merged
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 update to the conda environment causes problems if it happens in the middle of running with the conda environment elsewhere. (A likely time this might happen is when creating a build matrix with many compilers and/or MPI implementations, where you want to start running before all builds have completed.) It was always intended as a "safety" measure to ensure that ESMF comes from spack when we want that. There's no indication that isn't happening anyway.