Howard Pritchard

The problem is the lock is taken first in the call to ```mca_base_source_register ``` which then makes a call to ```mca_base_source_get_by_name``` which then also tries to take the lock. As...

It is possible the number of sources can increase during an application run (see section 15.3.8 of the MPI 4.1 standard), so there probably should be locking besides just in...

@kingshuk00 you are correct about the two unaddressed review comments. And i am of the opinion as well that this is too ambitious for the 6.0.x branch/release time frame. I...

something is broken with MPI4PY. The error is almost certainly not related to changes made in this PR.

@dalcinl would you have suggestions on debugging what's going on with mpi4py? it looks like some kind of problem with generation of mpi4py internal docs?

Let me know if you want help with the python binding infrastructure.

@edgargabriel added new data type to the bindings code to add this new use of ```const MPI_Request reqs[]``` in the standard.

I'll work on the fortran but that will have to wait till later in the week.

note that mpi4py is probably not testing this since it keys off our MPI_Get_version return values for major/minor. @edgargabriel have you tested mpi4py with VERSION faked to return 4.1?

@edgargabriel i pushed the remainder of the fortran related files to the PR - hopefully.