don't use harmful patch for h5py 2.10.0 with foss/2020a + pull out h5py 2.10.0 easyconfig using intel/2020a #10630
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.
The saga continues...
The patch added in #10626 isn't working out well, since it has the nasty side-effect of changing the default auto-
MPI_Initbehavior ofmpi4py, which causes surprises for any Python scripts using bothh5pyandmpi4py.A better fix that doesn't involve disabling the auto-init done by
mpi4py(just postponing it until actual MPI features are being used) is being discussed in h5py/h5py#1544, but it doesn't seem like it will be a trivial change.Since the problem only presents itself when using
intel/2020a