numba-mpi 1.1.2__tar.gz → 1.1.4__tar.gz

{numba_mpi-1.1.2 → numba_mpi-1.1.4}/.github/workflows/readme_snippets.yml

@@ -16,8 +16,8 @@ jobs:
   python:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
-      - uses: actions/setup-python@v1
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
         with:
           python-version: "3.10"
       - uses: mpi4py/setup-mpi@v1

{numba_mpi-1.1.2 → numba_mpi-1.1.4}/.github/workflows/tests+pypi.yml

@@ -18,10 +18,10 @@ jobs:
   pylint:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v4
     - uses: mpi4py/setup-mpi@v1
     - name: Set up Python
-      uses: actions/setup-python@v2
+      uses: actions/setup-python@v5
       with:
         python-version: "3.10"
     - name: Install dependencies
@@ -38,11 +38,11 @@ jobs:
   precommit:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
       - name: Set up Python
-        uses: actions/setup-python@v1
+        uses: actions/setup-python@v5
         with:
-          python-version: "3.10" 
+          python-version: "3.10"
       - name: Linting
         run: |
           pip install pre-commit
@@ -55,10 +55,10 @@ jobs:
     permissions:
       contents: write
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
         with:
           persist-credentials: false
-      - uses: actions/setup-python@v2
+      - uses: actions/setup-python@v5
         with:
           python-version: "3.10"
       - uses: mpi4py/setup-mpi@v1
@@ -78,9 +78,9 @@ jobs:
   zenodo_json:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
       - uses: notiz-dev/github-action-json-property@release
-        with: 
+        with:
           path: '.zenodo.json'
           prop_path: 'creators'
 
@@ -89,42 +89,53 @@ jobs:
     strategy:
       matrix:
         mpi-np: [2, 3]
-        platform: [ubuntu-latest, macos-13, windows-latest]
-        python-version: ["3.8", "3.9", "3.10", "3.11", "3.12"]
+        platform:
+          - ubuntu-latest
+          - windows-latest
+          - macos-13          # arch: Intel
+          - macos-15          # arch: arm64
+        python-version: ["3.9", "3.10", "3.11", "3.12", "3.13"]
         mpi: [ 'mpich', 'openmpi', 'msmpi', 'intelmpi']
         exclude:
         - platform: macos-13
           mpi: msmpi
         - platform: macos-13
           mpi: intelmpi
-        - platform: macos-13
+        - platform: macos-13   # TODO: # 163
+          mpi: openmpi
+        - platform: macos-15
+          mpi: msmpi
+        - platform: macos-15
+          mpi: intelmpi
+        - platform: macos-15
           mpi: openmpi
         - platform: ubuntu-latest
           mpi: msmpi
+        - platform: ubuntu-latest # TODO: #162
+          mpi: mpich
         - platform: windows-latest
           mpi: mpich
         - platform: windows-latest
           mpi: openmpi
         - platform: windows-latest
           mpi: intelmpi
-          
+
         # https://github.com/numba-mpi/numba-mpi/issues/69
-        - platform: ubuntu-latest
-          python-version: 3.8
-          mpi: mpich
         - platform: ubuntu-latest
           python-version: 3.9
           mpi: mpich
       fail-fast: false
     runs-on: ${{ matrix.platform }}
     steps:
-      - uses: actions/checkout@v2
-      - uses: actions/setup-python@v1
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
         with:
           python-version: ${{ matrix.python-version }}
       - uses: mpi4py/setup-mpi@v1
         with:
           mpi: ${{ matrix.mpi }}
+      - if: ${{ matrix.platform == 'macos-15' }}
+        run: echo DYLD_FALLBACK_LIBRARY_PATH="/opt/homebrew/lib:/usr/lib:$DYLD_FALLBACK_LIBRARY_PATH" >> $GITHUB_ENV
       - if: matrix.mpi == 'intelmpi'
         run: |
           # checking if multiple MPI libs are OK
@@ -165,13 +176,22 @@ jobs:
           cd /tmp  # make sure local files are not picked up
           python -We -c "import numba_mpi"
 
-      - if: github.event_name == 'push' && github.ref == 'refs/heads/main'
+      - if: |-
+          ${{
+            github.repository == 'numba-mpi/numba-mpi' &&
+            github.event_name == 'push' &&
+            github.ref == 'refs/heads/main'
+          }}
         uses: pypa/gh-action-pypi-publish@release/v1.12
         with:
           attestations: false
           repository_url: https://test.pypi.org/legacy/
 
-      - if: startsWith(github.ref, 'refs/tags')
+      - if: |-
+          ${{
+            github.repository == 'numba-mpi/numba-mpi' &&
+            startsWith(github.ref, 'refs/tags')
+          }}
         uses: pypa/gh-action-pypi-publish@release/v1.12
         with:
           attestations: false

{numba_mpi-1.1.2/numba_mpi.egg-info → numba_mpi-1.1.4}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.4
 Name: numba-mpi
-Version: 1.1.2
+Version: 1.1.4
 Summary: Numba @jittable MPI wrappers tested on Linux, macOS and Windows
 Home-page: https://github.com/numba-mpi/numba-mpi
 Author: https://github.com/numba-mpi/numba-mpi/graphs/contributors
@@ -18,6 +18,17 @@ Requires-Dist: psutil
 Provides-Extra: tests
 Requires-Dist: pytest<8.0.0; extra == "tests"
 Requires-Dist: py-pde; extra == "tests"
+Dynamic: author
+Dynamic: description
+Dynamic: description-content-type
+Dynamic: home-page
+Dynamic: license
+Dynamic: license-file
+Dynamic: project-url
+Dynamic: provides-extra
+Dynamic: requires-dist
+Dynamic: requires-python
+Dynamic: summary
 
 # <img src="https://raw.githubusercontent.com/numba-mpi/numba-mpi/main/.github/numba_mpi_logo.png" width=128 height=142 alt="numba-mpi logo"> numba-mpi
 
@@ -35,31 +46,32 @@ Requires-Dist: py-pde; extra == "tests"
 [![DOI](https://zenodo.org/badge/316911228.svg)](https://zenodo.org/badge/latestdoi/316911228)
 
 ### Overview
-numba-mpi provides Python wrappers to the C MPI API callable from within [Numba JIT-compiled code](https://numba.readthedocs.io/en/stable/user/jit.html) (@jit mode). For an outline of the project, rationale, architecture, and features, refer to: [numba-mpi arXiv e-print](https://doi.org/10.48550/arXiv.2407.13712) (please cite if numba-mpi is used in your research).
+numba-mpi provides Python wrappers to the C MPI API callable from within [Numba JIT-compiled code](https://numba.readthedocs.io/en/stable/user/jit.html) (@jit mode). For an outline of the project, rationale, architecture, and features, refer to: [numba-mpi paper in SoftwareX (open access)](https://www.sciencedirect.com/science/article/pii/S235271102400267X) (please cite if numba-mpi is used in your research).
 
 Support is provided for a subset of MPI routines covering: `size`/`rank`, `send`/`recv`, `allreduce`, `reduce`, `bcast`, `scatter`/`gather` & `allgather`, `barrier`, `wtime`
 and basic asynchronous communication with `isend`/`irecv` (only for contiguous arrays); for request handling including `wait`/`waitall`/`waitany` and `test`/`testall`/`testany`.
 
-The API uses NumPy and supports both numeric and character datatypes (e.g., `broadcast`). 
+The API uses NumPy and supports both numeric and character datatypes (e.g., `broadcast`).
 Auto-generated docstring-based API docs are published on the web: https://numba-mpi.github.io/numba-mpi
 
-Packages can be obtained from 
-  [PyPI](https://pypi.org/project/numba-mpi), 
-  [Conda Forge](https://anaconda.org/conda-forge/numba-mpi), 
+Packages can be obtained from
+  [PyPI](https://pypi.org/project/numba-mpi),
+  [Conda Forge](https://anaconda.org/conda-forge/numba-mpi),
   [Arch Linux](https://aur.archlinux.org/packages/python-numba-mpi)
   or by invoking `pip install git+https://github.com/numba-mpi/numba-mpi.git`.
 
 numba-mpi is a pure-Python package.
 The codebase includes a test suite used through the GitHub Actions workflows ([thanks to mpi4py's setup-mpi](https://github.com/mpi4py/setup-mpi)!)
-for automated testing on: Linux ([MPICH](https://www.mpich.org/), [OpenMPI](https://www.open-mpi.org/doc/) 
-& [Intel MPI](https://www.intel.com/content/www/us/en/developer/tools/oneapi/mpi-library.html)), 
-macOS ([MPICH](https://www.mpich.org/) & [OpenMPI](https://www.open-mpi.org/doc/)) and 
-Windows ([MS MPI](https://docs.microsoft.com/en-us/message-passing-interface/microsoft-mpi)).
+for automated testing on: Linux ([MPICH](https://www.mpich.org/), [OpenMPI](https://www.open-mpi.org/doc/)
+& [Intel MPI](https://www.intel.com/content/www/us/en/developer/tools/oneapi/mpi-library.html)),
+macOS ([MPICH](https://www.mpich.org/) & [OpenMPI](https://www.open-mpi.org/doc/)) and
+Windows ([MS MPI](https://docs.microsoft.com/en-us/message-passing-interface/microsoft-mpi)). Note, that some of those
+combinations may not be fully supported yet - see [Known Issues](#known-issues) for more information.
 
 Features that are not implemented yet include (help welcome!):
 - support for non-default communicators
 - support for `MPI_IN_PLACE` in `[all]gather`/`scatter` and `allreduce`
-- support for `MPI_Type_create_struct` (Numpy structured arrays) 
+- support for `MPI_Type_create_struct` (Numpy structured arrays)
 - ...
 
 ### Hello world send/recv example:
@@ -82,21 +94,21 @@ hello()
 ### Example comparing numba-mpi vs. mpi4py performance:
 
 The example below compares `Numba`+`mpi4py` vs. `Numba`+`numba-mpi` performance.
-The sample code estimates $\pi$ by numerical integration of $\int_0^1 (4/(1+x^2))dx=\pi$ 
-dividing the workload into `n_intervals` handled by separate MPI processes 
+The sample code estimates $\pi$ by numerical integration of $\int_0^1 (4/(1+x^2))dx=\pi$
+dividing the workload into `n_intervals` handled by separate MPI processes
 and then obtaining a sum using `allreduce` (see, e.g., analogous [Matlab docs example](https://www.mathworks.com/help/parallel-computing/numerical-estimation-of-pi-using-message-passing.html)).
 The computation is carried out in a JIT-compiled function `get_pi_part()` and is repeated
-`N_TIMES`. The repetitions and the MPI-handled reduction are done outside or 
+`N_TIMES`. The repetitions and the MPI-handled reduction are done outside or
 inside of the JIT-compiled block for `mpi4py` and `numba-mpi`, respectively.
 Timing is repeated `N_REPEAT` times and the minimum time is reported.
 The generated plot shown below depicts the speedup obtained by replacing `mpi4py`
-with `numba_mpi`, plotted as a function of `N_TIMES / n_intervals` - the number of MPI calls per 
+with `numba_mpi`, plotted as a function of `N_TIMES / n_intervals` - the number of MPI calls per
 interval. The speedup, which stems from avoiding roundtrips between JIT-compiled
 and Python code is significant (150%-300%) in all cases. The more often communication
-is needed (smaller `n_intervals`), the larger the measured speedup. Note that nothing 
+is needed (smaller `n_intervals`), the larger the measured speedup. Note that nothing
 in the actual number crunching (within the `get_pi_part()` function) or in the employed communication logic
 (handled by the same MPI library) differs between the `mpi4py` or `numba-mpi` solutions.
-These are the overhead of `mpi4py` higher-level abstractions and the overhead of 
+These are the overhead of `mpi4py` higher-level abstractions and the overhead of
 repeatedly entering and leaving the JIT-compiled block if using `mpi4py`, which can be
 eliminated by using `numba-mpi`, and which the measured differences in execution time
 stem from.
@@ -156,6 +168,14 @@ if numba_mpi.rank() == 0:
 
 ![plot](https://github.com/numba-mpi/numba-mpi/releases/download/tip/readme_plot.png)
 
+### Known Issues
+
+**NOTE**: Issues listed below only relate to combinations of platforms and MPI distributions that we target to support, but due to various reason are currently not working and are temporarily excluded from automated testing:
+
+- tests on Ubuntu 2024.4 that use MPICH are not run due to failures caused by newer version of MPICH (`4.2.0`); note, that previous tests ran
+using version `4.0.2` of MPICH (that is installed by default on Ubuntu 2022.4 using `apt`) were passing (see [related issue](https://github.com/numba-mpi/numba-mpi/issues/162) - TODO #162),
+- tests on Intel MacOS (v13) that use OpenMPI are currently not run due to failures being under investigation (see [related issue](https://github.com/numba-mpi/numba-mpi/issues/163)  - TODO #163),
+- `numba-mpi` currently does not support ARM-based MacOS, due to required code improvement (see [related issue](https://github.com/numba-mpi/numba-mpi/issues/164) - TODO #164).
 
 ### MPI resources on the web:
 
@@ -177,11 +197,10 @@ if numba_mpi.rank() == 0:
 
 ### Acknowledgements:
 
-We thank [all contributors](https://github.com/numba-mpi/numba-mpi/graphs/contributors) and users who reported feedback to the project 
+We thank [all contributors](https://github.com/numba-mpi/numba-mpi/graphs/contributors) and users who reported feedback to the project
   through [GitHub issues](https://github.com/numba-mpi/numba-mpi/issues).
 
 Development of numba-mpi has been supported by the [Polish National Science Centre](https://ncn.gov.pl/en) (grant no. 2020/39/D/ST10/01220),
-  the [Max Planck Society](https://www.mpg.de/en) and the [European Union](https://erc.europa.eu/) (ERC, EmulSim, 101044662). 
-We further acknowledge Poland’s high-performance computing infrastructure [PLGrid](https://plgrid.pl) (HPC Centers: [ACK Cyfronet AGH](https://www.cyfronet.pl/en)) 
+  the [Max Planck Society](https://www.mpg.de/en) and the [European Union](https://erc.europa.eu/) (ERC, EmulSim, 101044662).
+We further acknowledge Poland’s high-performance computing infrastructure [PLGrid](https://plgrid.pl) (HPC Centers: [ACK Cyfronet AGH](https://www.cyfronet.pl/en))
   for providing computer facilities and support within computational grant no. PLG/2023/016369.
-

{numba_mpi-1.1.2 → numba_mpi-1.1.4}/README.md

@@ -14,31 +14,32 @@
 [![DOI](https://zenodo.org/badge/316911228.svg)](https://zenodo.org/badge/latestdoi/316911228)
 
 ### Overview
-numba-mpi provides Python wrappers to the C MPI API callable from within [Numba JIT-compiled code](https://numba.readthedocs.io/en/stable/user/jit.html) (@jit mode). For an outline of the project, rationale, architecture, and features, refer to: [numba-mpi arXiv e-print](https://doi.org/10.48550/arXiv.2407.13712) (please cite if numba-mpi is used in your research).
+numba-mpi provides Python wrappers to the C MPI API callable from within [Numba JIT-compiled code](https://numba.readthedocs.io/en/stable/user/jit.html) (@jit mode). For an outline of the project, rationale, architecture, and features, refer to: [numba-mpi paper in SoftwareX (open access)](https://www.sciencedirect.com/science/article/pii/S235271102400267X) (please cite if numba-mpi is used in your research).
 
 Support is provided for a subset of MPI routines covering: `size`/`rank`, `send`/`recv`, `allreduce`, `reduce`, `bcast`, `scatter`/`gather` & `allgather`, `barrier`, `wtime`
 and basic asynchronous communication with `isend`/`irecv` (only for contiguous arrays); for request handling including `wait`/`waitall`/`waitany` and `test`/`testall`/`testany`.
 
-The API uses NumPy and supports both numeric and character datatypes (e.g., `broadcast`). 
+The API uses NumPy and supports both numeric and character datatypes (e.g., `broadcast`).
 Auto-generated docstring-based API docs are published on the web: https://numba-mpi.github.io/numba-mpi
 
-Packages can be obtained from 
-  [PyPI](https://pypi.org/project/numba-mpi), 
-  [Conda Forge](https://anaconda.org/conda-forge/numba-mpi), 
+Packages can be obtained from
+  [PyPI](https://pypi.org/project/numba-mpi),
+  [Conda Forge](https://anaconda.org/conda-forge/numba-mpi),
   [Arch Linux](https://aur.archlinux.org/packages/python-numba-mpi)
   or by invoking `pip install git+https://github.com/numba-mpi/numba-mpi.git`.
 
 numba-mpi is a pure-Python package.
 The codebase includes a test suite used through the GitHub Actions workflows ([thanks to mpi4py's setup-mpi](https://github.com/mpi4py/setup-mpi)!)
-for automated testing on: Linux ([MPICH](https://www.mpich.org/), [OpenMPI](https://www.open-mpi.org/doc/) 
-& [Intel MPI](https://www.intel.com/content/www/us/en/developer/tools/oneapi/mpi-library.html)), 
-macOS ([MPICH](https://www.mpich.org/) & [OpenMPI](https://www.open-mpi.org/doc/)) and 
-Windows ([MS MPI](https://docs.microsoft.com/en-us/message-passing-interface/microsoft-mpi)).
+for automated testing on: Linux ([MPICH](https://www.mpich.org/), [OpenMPI](https://www.open-mpi.org/doc/)
+& [Intel MPI](https://www.intel.com/content/www/us/en/developer/tools/oneapi/mpi-library.html)),
+macOS ([MPICH](https://www.mpich.org/) & [OpenMPI](https://www.open-mpi.org/doc/)) and
+Windows ([MS MPI](https://docs.microsoft.com/en-us/message-passing-interface/microsoft-mpi)). Note, that some of those
+combinations may not be fully supported yet - see [Known Issues](#known-issues) for more information.
 
 Features that are not implemented yet include (help welcome!):
 - support for non-default communicators
 - support for `MPI_IN_PLACE` in `[all]gather`/`scatter` and `allreduce`
-- support for `MPI_Type_create_struct` (Numpy structured arrays) 
+- support for `MPI_Type_create_struct` (Numpy structured arrays)
 - ...
 
 ### Hello world send/recv example:
@@ -61,21 +62,21 @@ hello()
 ### Example comparing numba-mpi vs. mpi4py performance:
 
 The example below compares `Numba`+`mpi4py` vs. `Numba`+`numba-mpi` performance.
-The sample code estimates $\pi$ by numerical integration of $\int_0^1 (4/(1+x^2))dx=\pi$ 
-dividing the workload into `n_intervals` handled by separate MPI processes 
+The sample code estimates $\pi$ by numerical integration of $\int_0^1 (4/(1+x^2))dx=\pi$
+dividing the workload into `n_intervals` handled by separate MPI processes
 and then obtaining a sum using `allreduce` (see, e.g., analogous [Matlab docs example](https://www.mathworks.com/help/parallel-computing/numerical-estimation-of-pi-using-message-passing.html)).
 The computation is carried out in a JIT-compiled function `get_pi_part()` and is repeated
-`N_TIMES`. The repetitions and the MPI-handled reduction are done outside or 
+`N_TIMES`. The repetitions and the MPI-handled reduction are done outside or
 inside of the JIT-compiled block for `mpi4py` and `numba-mpi`, respectively.
 Timing is repeated `N_REPEAT` times and the minimum time is reported.
 The generated plot shown below depicts the speedup obtained by replacing `mpi4py`
-with `numba_mpi`, plotted as a function of `N_TIMES / n_intervals` - the number of MPI calls per 
+with `numba_mpi`, plotted as a function of `N_TIMES / n_intervals` - the number of MPI calls per
 interval. The speedup, which stems from avoiding roundtrips between JIT-compiled
 and Python code is significant (150%-300%) in all cases. The more often communication
-is needed (smaller `n_intervals`), the larger the measured speedup. Note that nothing 
+is needed (smaller `n_intervals`), the larger the measured speedup. Note that nothing
 in the actual number crunching (within the `get_pi_part()` function) or in the employed communication logic
 (handled by the same MPI library) differs between the `mpi4py` or `numba-mpi` solutions.
-These are the overhead of `mpi4py` higher-level abstractions and the overhead of 
+These are the overhead of `mpi4py` higher-level abstractions and the overhead of
 repeatedly entering and leaving the JIT-compiled block if using `mpi4py`, which can be
 eliminated by using `numba-mpi`, and which the measured differences in execution time
 stem from.
@@ -135,6 +136,14 @@ if numba_mpi.rank() == 0:
 
 ![plot](https://github.com/numba-mpi/numba-mpi/releases/download/tip/readme_plot.png)
 
+### Known Issues
+
+**NOTE**: Issues listed below only relate to combinations of platforms and MPI distributions that we target to support, but due to various reason are currently not working and are temporarily excluded from automated testing:
+
+- tests on Ubuntu 2024.4 that use MPICH are not run due to failures caused by newer version of MPICH (`4.2.0`); note, that previous tests ran
+using version `4.0.2` of MPICH (that is installed by default on Ubuntu 2022.4 using `apt`) were passing (see [related issue](https://github.com/numba-mpi/numba-mpi/issues/162) - TODO #162),
+- tests on Intel MacOS (v13) that use OpenMPI are currently not run due to failures being under investigation (see [related issue](https://github.com/numba-mpi/numba-mpi/issues/163)  - TODO #163),
+- `numba-mpi` currently does not support ARM-based MacOS, due to required code improvement (see [related issue](https://github.com/numba-mpi/numba-mpi/issues/164) - TODO #164).
 
 ### MPI resources on the web:
 
@@ -156,11 +165,10 @@ if numba_mpi.rank() == 0:
 
 ### Acknowledgements:
 
-We thank [all contributors](https://github.com/numba-mpi/numba-mpi/graphs/contributors) and users who reported feedback to the project 
+We thank [all contributors](https://github.com/numba-mpi/numba-mpi/graphs/contributors) and users who reported feedback to the project
   through [GitHub issues](https://github.com/numba-mpi/numba-mpi/issues).
 
 Development of numba-mpi has been supported by the [Polish National Science Centre](https://ncn.gov.pl/en) (grant no. 2020/39/D/ST10/01220),
-  the [Max Planck Society](https://www.mpg.de/en) and the [European Union](https://erc.europa.eu/) (ERC, EmulSim, 101044662). 
-We further acknowledge Poland’s high-performance computing infrastructure [PLGrid](https://plgrid.pl) (HPC Centers: [ACK Cyfronet AGH](https://www.cyfronet.pl/en)) 
+  the [Max Planck Society](https://www.mpg.de/en) and the [European Union](https://erc.europa.eu/) (ERC, EmulSim, 101044662).
+We further acknowledge Poland’s high-performance computing infrastructure [PLGrid](https://plgrid.pl) (HPC Centers: [ACK Cyfronet AGH](https://www.cyfronet.pl/en))
   for providing computer facilities and support within computational grant no. PLG/2023/016369.
-

{numba_mpi-1.1.2 → numba_mpi-1.1.4}/numba_mpi/api/requests.py

@@ -1,5 +1,5 @@
-""" Utilities for handling MPI_Requests with respective Wait and Test function
-    wrappers.
+"""Utilities for handling MPI_Requests with respective Wait and Test function
+wrappers.
 """
 
 import ctypes

{numba_mpi-1.1.2 → numba_mpi-1.1.4}/numba_mpi/common.py

@@ -2,6 +2,7 @@
 
 import ctypes
 import os
+import sys
 from ctypes.util import find_library
 from pathlib import Path
 
@@ -72,6 +73,12 @@ else:
             break
 
 if LIB is None:
+    if sys.platform == "darwin":
+        raise RuntimeError(
+            """MPI library not found, if MPI was installed with Homebrew, export the following:
+            DYLD_FALLBACK_LIBRARY_PATH="/opt/homebrew/lib:/usr/lib:$DYLD_FALLBACK_LIBRARY_PATH
+            """
+        )
     raise RuntimeError("no MPI library found")
 
 libmpi = ctypes.CDLL(LIB)

{numba_mpi-1.1.2 → numba_mpi-1.1.4/numba_mpi.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.4
 Name: numba-mpi
-Version: 1.1.2
+Version: 1.1.4
 Summary: Numba @jittable MPI wrappers tested on Linux, macOS and Windows
 Home-page: https://github.com/numba-mpi/numba-mpi
 Author: https://github.com/numba-mpi/numba-mpi/graphs/contributors
@@ -18,6 +18,17 @@ Requires-Dist: psutil
 Provides-Extra: tests
 Requires-Dist: pytest<8.0.0; extra == "tests"
 Requires-Dist: py-pde; extra == "tests"
+Dynamic: author
+Dynamic: description
+Dynamic: description-content-type
+Dynamic: home-page
+Dynamic: license
+Dynamic: license-file
+Dynamic: project-url
+Dynamic: provides-extra
+Dynamic: requires-dist
+Dynamic: requires-python
+Dynamic: summary
 
 # <img src="https://raw.githubusercontent.com/numba-mpi/numba-mpi/main/.github/numba_mpi_logo.png" width=128 height=142 alt="numba-mpi logo"> numba-mpi
 
@@ -35,31 +46,32 @@ Requires-Dist: py-pde; extra == "tests"
 [![DOI](https://zenodo.org/badge/316911228.svg)](https://zenodo.org/badge/latestdoi/316911228)
 
 ### Overview
-numba-mpi provides Python wrappers to the C MPI API callable from within [Numba JIT-compiled code](https://numba.readthedocs.io/en/stable/user/jit.html) (@jit mode). For an outline of the project, rationale, architecture, and features, refer to: [numba-mpi arXiv e-print](https://doi.org/10.48550/arXiv.2407.13712) (please cite if numba-mpi is used in your research).
+numba-mpi provides Python wrappers to the C MPI API callable from within [Numba JIT-compiled code](https://numba.readthedocs.io/en/stable/user/jit.html) (@jit mode). For an outline of the project, rationale, architecture, and features, refer to: [numba-mpi paper in SoftwareX (open access)](https://www.sciencedirect.com/science/article/pii/S235271102400267X) (please cite if numba-mpi is used in your research).
 
 Support is provided for a subset of MPI routines covering: `size`/`rank`, `send`/`recv`, `allreduce`, `reduce`, `bcast`, `scatter`/`gather` & `allgather`, `barrier`, `wtime`
 and basic asynchronous communication with `isend`/`irecv` (only for contiguous arrays); for request handling including `wait`/`waitall`/`waitany` and `test`/`testall`/`testany`.
 
-The API uses NumPy and supports both numeric and character datatypes (e.g., `broadcast`). 
+The API uses NumPy and supports both numeric and character datatypes (e.g., `broadcast`).
 Auto-generated docstring-based API docs are published on the web: https://numba-mpi.github.io/numba-mpi
 
-Packages can be obtained from 
-  [PyPI](https://pypi.org/project/numba-mpi), 
-  [Conda Forge](https://anaconda.org/conda-forge/numba-mpi), 
+Packages can be obtained from
+  [PyPI](https://pypi.org/project/numba-mpi),
+  [Conda Forge](https://anaconda.org/conda-forge/numba-mpi),
   [Arch Linux](https://aur.archlinux.org/packages/python-numba-mpi)
   or by invoking `pip install git+https://github.com/numba-mpi/numba-mpi.git`.
 
 numba-mpi is a pure-Python package.
 The codebase includes a test suite used through the GitHub Actions workflows ([thanks to mpi4py's setup-mpi](https://github.com/mpi4py/setup-mpi)!)
-for automated testing on: Linux ([MPICH](https://www.mpich.org/), [OpenMPI](https://www.open-mpi.org/doc/) 
-& [Intel MPI](https://www.intel.com/content/www/us/en/developer/tools/oneapi/mpi-library.html)), 
-macOS ([MPICH](https://www.mpich.org/) & [OpenMPI](https://www.open-mpi.org/doc/)) and 
-Windows ([MS MPI](https://docs.microsoft.com/en-us/message-passing-interface/microsoft-mpi)).
+for automated testing on: Linux ([MPICH](https://www.mpich.org/), [OpenMPI](https://www.open-mpi.org/doc/)
+& [Intel MPI](https://www.intel.com/content/www/us/en/developer/tools/oneapi/mpi-library.html)),
+macOS ([MPICH](https://www.mpich.org/) & [OpenMPI](https://www.open-mpi.org/doc/)) and
+Windows ([MS MPI](https://docs.microsoft.com/en-us/message-passing-interface/microsoft-mpi)). Note, that some of those
+combinations may not be fully supported yet - see [Known Issues](#known-issues) for more information.
 
 Features that are not implemented yet include (help welcome!):
 - support for non-default communicators
 - support for `MPI_IN_PLACE` in `[all]gather`/`scatter` and `allreduce`
-- support for `MPI_Type_create_struct` (Numpy structured arrays) 
+- support for `MPI_Type_create_struct` (Numpy structured arrays)
 - ...
 
 ### Hello world send/recv example:
@@ -82,21 +94,21 @@ hello()
 ### Example comparing numba-mpi vs. mpi4py performance:
 
 The example below compares `Numba`+`mpi4py` vs. `Numba`+`numba-mpi` performance.
-The sample code estimates $\pi$ by numerical integration of $\int_0^1 (4/(1+x^2))dx=\pi$ 
-dividing the workload into `n_intervals` handled by separate MPI processes 
+The sample code estimates $\pi$ by numerical integration of $\int_0^1 (4/(1+x^2))dx=\pi$
+dividing the workload into `n_intervals` handled by separate MPI processes
 and then obtaining a sum using `allreduce` (see, e.g., analogous [Matlab docs example](https://www.mathworks.com/help/parallel-computing/numerical-estimation-of-pi-using-message-passing.html)).
 The computation is carried out in a JIT-compiled function `get_pi_part()` and is repeated
-`N_TIMES`. The repetitions and the MPI-handled reduction are done outside or 
+`N_TIMES`. The repetitions and the MPI-handled reduction are done outside or
 inside of the JIT-compiled block for `mpi4py` and `numba-mpi`, respectively.
 Timing is repeated `N_REPEAT` times and the minimum time is reported.
 The generated plot shown below depicts the speedup obtained by replacing `mpi4py`
-with `numba_mpi`, plotted as a function of `N_TIMES / n_intervals` - the number of MPI calls per 
+with `numba_mpi`, plotted as a function of `N_TIMES / n_intervals` - the number of MPI calls per
 interval. The speedup, which stems from avoiding roundtrips between JIT-compiled
 and Python code is significant (150%-300%) in all cases. The more often communication
-is needed (smaller `n_intervals`), the larger the measured speedup. Note that nothing 
+is needed (smaller `n_intervals`), the larger the measured speedup. Note that nothing
 in the actual number crunching (within the `get_pi_part()` function) or in the employed communication logic
 (handled by the same MPI library) differs between the `mpi4py` or `numba-mpi` solutions.
-These are the overhead of `mpi4py` higher-level abstractions and the overhead of 
+These are the overhead of `mpi4py` higher-level abstractions and the overhead of
 repeatedly entering and leaving the JIT-compiled block if using `mpi4py`, which can be
 eliminated by using `numba-mpi`, and which the measured differences in execution time
 stem from.
@@ -156,6 +168,14 @@ if numba_mpi.rank() == 0:
 
 ![plot](https://github.com/numba-mpi/numba-mpi/releases/download/tip/readme_plot.png)
 
+### Known Issues
+
+**NOTE**: Issues listed below only relate to combinations of platforms and MPI distributions that we target to support, but due to various reason are currently not working and are temporarily excluded from automated testing:
+
+- tests on Ubuntu 2024.4 that use MPICH are not run due to failures caused by newer version of MPICH (`4.2.0`); note, that previous tests ran
+using version `4.0.2` of MPICH (that is installed by default on Ubuntu 2022.4 using `apt`) were passing (see [related issue](https://github.com/numba-mpi/numba-mpi/issues/162) - TODO #162),
+- tests on Intel MacOS (v13) that use OpenMPI are currently not run due to failures being under investigation (see [related issue](https://github.com/numba-mpi/numba-mpi/issues/163)  - TODO #163),
+- `numba-mpi` currently does not support ARM-based MacOS, due to required code improvement (see [related issue](https://github.com/numba-mpi/numba-mpi/issues/164) - TODO #164).
 
 ### MPI resources on the web:
 
@@ -177,11 +197,10 @@ if numba_mpi.rank() == 0:
 
 ### Acknowledgements:
 
-We thank [all contributors](https://github.com/numba-mpi/numba-mpi/graphs/contributors) and users who reported feedback to the project 
+We thank [all contributors](https://github.com/numba-mpi/numba-mpi/graphs/contributors) and users who reported feedback to the project
   through [GitHub issues](https://github.com/numba-mpi/numba-mpi/issues).
 
 Development of numba-mpi has been supported by the [Polish National Science Centre](https://ncn.gov.pl/en) (grant no. 2020/39/D/ST10/01220),
-  the [Max Planck Society](https://www.mpg.de/en) and the [European Union](https://erc.europa.eu/) (ERC, EmulSim, 101044662). 
-We further acknowledge Poland’s high-performance computing infrastructure [PLGrid](https://plgrid.pl) (HPC Centers: [ACK Cyfronet AGH](https://www.cyfronet.pl/en)) 
+  the [Max Planck Society](https://www.mpg.de/en) and the [European Union](https://erc.europa.eu/) (ERC, EmulSim, 101044662).
+We further acknowledge Poland’s high-performance computing infrastructure [PLGrid](https://plgrid.pl) (HPC Centers: [ACK Cyfronet AGH](https://www.cyfronet.pl/en))
   for providing computer facilities and support within computational grant no. PLG/2023/016369.
-

{numba_mpi-1.1.2 → numba_mpi-1.1.4}/setup.py

@@ -1,4 +1,4 @@
-""" the magick behind ``pip install ...`` """
+"""the magick behind ``pip install ...``"""
 
 from setuptools import find_packages, setup
 
@@ -18,7 +18,7 @@ setup(
     url="https://github.com/numba-mpi/numba-mpi",
     author="https://github.com/numba-mpi/numba-mpi/graphs/contributors",
     use_scm_version={
-        "local_scheme": lambda _: "",
+        "local_scheme": "no-local-version",
         "version_scheme": "post-release",
     },
     python_requires=">=3.8",

{numba_mpi-1.1.2 → numba_mpi-1.1.4}/tests/api/test_bcast.py

@@ -15,8 +15,8 @@ def jit_bcast(data, root):
 
 @pytest.mark.parametrize("bcast", (jit_bcast.py_func, jit_bcast))
 @pytest.mark.parametrize("data_type", data_types)
-def test_bcast_np_array(data_type, bcast):
-    root = 0
+@pytest.mark.parametrize("root", range(mpi.size()))
+def test_bcast_np_array(data_type, bcast, root):
     data = np.empty(5, data_type).astype(dtype=data_type)
     datatobcast = get_random_array(5, data_type).astype(dtype=data_type)
 
@@ -34,8 +34,8 @@ def test_bcast_np_array(data_type, bcast):
     "stringtobcast",
     ("test bcast", pytest.param("żółć", marks=pytest.mark.xfail(strict=True))),
 )
-def test_bcast_string(stringtobcast):
-    root = 0
+@pytest.mark.parametrize("root", range(mpi.size()))
+def test_bcast_string(stringtobcast, root):
     datatobcast = np.array(stringtobcast, "c")
     data = np.empty_like(datatobcast)
 

{numba_mpi-1.1.2 → numba_mpi-1.1.4}/tests/test_paper_listings.py

@@ -1,4 +1,4 @@
-""" checks if listings from the paper run OK """
+"""checks if listings from the paper run OK"""
 
 import pathlib