Skip to content

Commit

Permalink
docs: Use better links for mpi4py
Browse files Browse the repository at this point in the history
I asked Lisandro what link we should use for mpi4py; he asked that we
use https://mpi4py.github.io/.

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
  • Loading branch information
jsquyres committed May 23, 2023
1 parent b471ee3 commit 45dc171
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/news/news-v5.0.x.rst
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ Open MPI version 5.0.0rc12
dynamic shared objects.
- Fix ``MPI_Session_init()`` bug if all previous sessions are
finalized.
- Fix `mpi4py <https://mpi4py.readthedocs.io/>`_ hang in
- Fix `mpi4py <https://mpi4py.github.io/>`_ hang in
``MPI_Intercomm_create_from_groups()``.
- Fix finalization segfault with OSHMEM 4.1.5.
- Improve AVX detection. Fixes ``op/avx`` link failure with the
Expand Down
2 changes: 1 addition & 1 deletion docs/tuning-apps/dynamic-loading.rst
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ operating systems use other suffixes, such as ``.so``):
.. note:: The above is just an example showing dynamic loading. If
you want to use MPI in Python, you are much better off using
`MPI4Py <https://mpi4py.readthedocs.io/en/stable/>`_.
`MPI4Py <https://mpi4py.github.io/>`_.

Other scripting languages should have similar options when dynamically
loading shared libraries.

0 comments on commit 45dc171

Please sign in to comment.