separating fake communicator from mpifile #286
Closed
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.
Isolating the FakeCommunicator class. It is a very useful class, but the star import from mpi4py affects mpi4py's behavior I do not need a whole MPI world or the world does not exist (running other types of parallelization).
This does not change the functionality of the
mpi.py
as the FakeCommunicator class is imported by it. It just makes sure that the FakeCommunicator can be imported in isolation.PR simonsobs/sotodlib#1096 depends on this