Alain Miniussi

I'm going to check why it hang. I'd like to point out that none of Boost.MPI function is supposed to map the MPI standard regarding serialized communication as there is...

There was a proposal in #72 to make the switch between the 2 implementation available at runtime, we still have that option if it comes down to that.

Would a `` // Uncomment if you don't want to use MPI_Probe and friends` //#define BOOST_MPI_NO_IMPROBE ``` Do the trick ?

So basically, what you want is a wait those behavior is: ``` while (request.active()) request.test(); ``` ?

So it should be possible to implement something sensible. The trick is to handle the status;

@xnox : Let's move this one here

Maybe we can export both **mpi** (to be inline with the current name) and **boost.mpi** **mpi** should probably be made obsolete.

That's probably the problem. When building from the git repository, the mpi.so file is droped in `./stage/lib/boost-python2.7/`. That should be in `./stage/lib/boost-python2.7/boost` with he appropriate `__init__.py`. I have no idea...

On my ubuntu box: ``` alainm@jarvis:~/views/boostorg/boost$ find /opt/boost-1.73.0/lib/ -name mpi.so /opt/boost-1.73.0/lib/boost-python3.6/mpi.so alainm@jarvis:~/views/boostorg/boost$ ```

Ok, I don't know if you had a chance to look at #112, but the issue has been discussed there. At this point, it's a manual packaging issue.