Actively maintained MPI implementationswrappers infor [[Python (programming language)|Python]] include: [[pyMPI]], mpi4py,<ref>{{cite web|url=https://codempi4py.googlereadthedocs.com/p/mpi4pyio/|title=Google Code Archive - Long-term storage for Google Code Project Hosting.|website=code.google.commpi4py}}</ref>, pypar,numba-mpi<ref>{{cite web|url=https://codepypi.google.comorg/p/pyparnumba-mpi}</|title=Google Coderef> Archiveand numba-jax<ref>{{cite Long-term storage for Google Code Project Hosting.web|websiteurl=codehttps://mpi4jax.googlereadthedocs.comio/|title=mpi4jax}}</ref> MYMPI,<ref>.
Now part of [http://sourceforge.net/projects/pydusa/ Pydusa]</ref> and the MPI submodule in [[ScientificPython]]. pyMPI is notable because it is a variant python interpreter, while pypar, MYMPI, and ScientificPython's module are import modules. They make it the coder's job to decide where the call to <code>MPI_Init</code> belongs.
Discontinued developments include: [[pyMPI]], pypar<ref>{{cite web|url=https://code.google.com/p/pypar/|title=Google Code Archive - Long-term storage for Google Code Project Hosting.|website=code.google.com}}</ref>, MYMPI<ref>Now part of [http://sourceforge.net/projects/pydusa/ Pydusa]</ref> and the MPI submodule in [[ScientificPython]].
In 2006<ref>{{cite web|url=https://www.boost.org/doc/libs/1_80_0/doc/html/mpi/history.html|title=Boost.MPI Revision History|website=www.boost.org}}</ref> the [[Boost C++ Libraries]] acquired Boost:MPI which included the MPI Python Bindings.<ref>{{cite web|url=http://www.boost.org/doc/libs/1_35_0/doc/html/mpi/python.html|title=Python Bindings - 1.35.0|website=www.boost.org}}</ref> This is of particular help for mixing C++ and Python. {{As of|2016|10}} Boost:MPI's Python bindings still have unfixed packaging bugs in [[CentOS]].<ref>{{cite web|url=https://bugs.centos.org/view.php?id=6498|title=0006498: Package boost-*mpi-python is missing python module - CentOS Bug Tracker|website=bugs.centos.org}}</ref>
