* 'develop' of https://github.com/boostorg/mpi: (54 commits)
  We want to skip C++ binding in underlying implementation (othewise, Open MPI does not give a choice), it's too late to avoid building them.
  typo in doc
  put status code in status files
  put status code in status files
  Use new library naming conventions.
  add test for wait_all on null request
  Make definition consistent with comment. We do not want the c++ bidings with OpenMPI
  split travis jobs
  Avoid a few warnings
  Use the same serialization code for python2 and python3 thank to bytesobject.h. Thanks to @xnox for the idea.
  Revert "Use the same serialization code for python2 and python3 thank to bytesobject.h."
  Use the same serialization code for python2 and python3 thank to bytesobject.h. Thanks to @xnox for the idea.
  Although single argument print () works in python2, it is still prudent to do have from __future__ import print_function as the first line of code in every file. Thanks to @xnox for the suggestion
  factorize
  have pick API work in both python 2 and 3
  Use neutral var name for buffer
  remove spurious extract and ()s
  We assume python2 pickle API, wich used str as buffers. We need something compatible with python3, which uses bytes. Common base is object
  use python3 compatible print
  For some reason mpi module is now at top level, adapt the mpi python test to that
  ...

…dded to each Boost library's meta json information for libraries in order to specify the minumum C++ standard compilation level. The value of this field matches one of the values for 'cxxstd' in Boost.Build. The purpose of doing this is to provide information for the Boost website documentation for each library which will specify the minimum C++ standard compilation that an end-user must employ in order to use the particular library. This will aid end-users who want to know if they can successfully use a Boost library based on their C++ compiler's compilation level, without having to search the library's documentation to find this out.

Based on MPI-3 MPI_Get_library_version() API.
On previous versions it returns an empty string.

…tions.

…mpi into maksim-0-fix_buffer_primitive_load_save

…e131

…pi into leha-bot-feature/mpi-3-library-version

…ove MPI3

Added MPI test in CTest framework

Don't use MPI constants as compile-time constants

Don't use MPI constants as compile-time constants

refs #144