Lisandro Dalcin

As I do not have access to Summit, it is almost impossible for me to figure out what's going on. When users have problems with mpi4py, the usually come to...

> And I heard MPIComExecutor was for compatibility legacy purposes right? That's not true, not at all. What is kind of "compatibility support" is using `mpiexec -n python -m mpi4py.futures...

Looks like there are some misunderstandings I should clarify. * As you are using `MPICommExecutor`, then you SHOULD NOT use `python -m mpi4py.futures ...` to run your script. The `-m...

Sending SIGINT is not enough to debug the issue. You will have to modify mpi4py's source code and add `print()` calls here and there so figure out where exactly the...

@profPlum Any update on this issue? Could you manage to get some help form Summit staff?

I believe they forgot. Otherwise why would MPI-4.0 have the following two getter routines with exactly the same signature, but only one for the setter? ```c int MPI_Get_elements_c(const MPI_Status *status,...

> I feel like rather the addition of `MPI_Get_elements_c` was a mistake Well, that's certainly a valid way to see it. But for the sake of consistency on naming conventions,...

> @dalcinl Shall we close this issue? Yes, sure.

@hzhou @raffenet Should we reopen this issue? As I do not have access to the in-development MPI standard documents, I'm not really sure whether `MPI_Status_set_elements_c` was added as an errata...

Guys, just a quick question. What the exact meaning of the "errata" label in the forum repo? Is this new routine part of MPI-4.0 or an upcoming minor revision MPI-4.1...