Updates the doc in CONTRIBUTING.rst for the new compile system. Adds doc, repo, issues links in pyproject.toml. CHANGELOG.

Author: fakufaku

CHANGELOG.rst

@@ -11,7 +11,14 @@ adheres to `Semantic Versioning <http://semver.org/spec/v2.0.0.html>`_.
 `Unreleased`_
 -------------
 
-Nothing yet.
+Changed
+~~~~~~~
+
+- Modernized the build system to use ``pyproject.toml`` and ``CMake``.
+- External dependencies (``Eigen``, ``nanoflann``, ``pybind11``) are now automatically managed via CMake's ``FetchContent``.
+- Switched to dynamic versioning using ``setuptools_scm``.
+- Relocated the test suite from the source package to a top-level ``tests/`` directory.
+- Update the continuous integration to use cibuildwheel to handle all platforms including manylinux.
 
 
 `0.10.0`_ - 2026-04-01

CONTRIBUTING.rst

@@ -24,16 +24,24 @@ We try to stick to `PEP8 <https://www.python.org/dev/peps/pep-0008/>`__
 as much as possible. Variables, functions, modules and packages should
 be in lowercase with underscores. Class names in CamelCase.
 
-We use `Black <https://github.com/psf/black>`__ to format the code and `isort <https://pycqa.github.io/isort/>`__ to sort the imports.
-The format will be automatically checked when doing a pull request so it is
-recommended to regularly run Black on the code.
-Please format your code as follows prior to commiting.
+We use `pre-commit <https://pre-commit.com/>`__ to manage code quality hooks,
+including `Black <https://github.com/psf/black>`__ for formatting and
+`isort <https://pycqa.github.io/isort/>`__ for sorting imports.
+The hooks will be automatically checked during pull requests.
+
+To set up the pre-commit hooks locally:
+
+.. code-block:: shell
+
+  pip install pre-commit
+  pre-commit install
+
+Once installed, the hooks will run automatically on every commit.
+You can also run them manually on all files:
 
 .. code-block:: shell
 
-  pip install black isort
-  black .
-  isort --profile black .
+  pre-commit run --all-files
 
 Documentation
 ~~~~~~~~~~~~~
@@ -51,79 +59,56 @@ We recommend the following steps for generating the documentation:
 -  Build and view the documentation locally with: ``make html``
 -  Open in your browser: ``docs/_build/html/index.html``
 
-Develop Locally
-~~~~~~~~~~~~~~~
-
-It can be convenient to develop and run tests locally.  In contrast to only
+It can be convenient to develop and run tests locally. In contrast to only
 using the package, you will then also need to compile the C++ extension for
-that. On Mac and Linux, GCC is required, while Visual C++ 14.0 is necessary for
-`windows <https://wiki.python.org/moin/WindowsCompilers>`__. 
-
-1. Get the source code. Use recursive close so that Eigen (a sub-module of this
-   repository) is also downloaded.
-
-   .. code-block:: shell
+that.
 
-       git clone --recursive git@github.com:LCAV/pyroomacoustics.git
+Requirements:
+- C++ compiler: GCC or Clang on Mac/Linux, Visual C++ 14.0+ on Windows.
+- **CMake** (version 3.10 or higher).
+- **pre-commit**
 
-   Alternatively, you can clone without the `--recursive` flag and directly
-   install the Eigen library. For macOS, you can find installation instruction
-   here: https://stackoverflow.com/a/35658421. After installation you can
-   create a symbolic link as such:
-
-    .. code-block:: shell
-
-        ln -s PATH_TO_EIGEN pyroomacoustics/libroom_src/ext/eigen/Eigen
-
-2. Install a few pre-requisites
-
-    .. code-block:: shell
-
-        pip install numpy Cython pybind11
-
-3. Compile locally
+1. Get the source code.
 
    .. code-block:: shell
 
-         python setup.py build_ext --inplace
-
-   On recent Mac OS (Mojave), it is necessary in some cases to add a
-   higher deployment target
+       git clone git@github.com:LCAV/pyroomacoustics.git
 
-   .. code-block:: shell
+   External dependencies (`Eigen`, `nanoflann`, `pybind11`) are automatically
+   downloaded during the build process using CMake's `FetchContent`.
 
-         MACOSX_DEPLOYMENT_TARGET=10.9 python setup.py build_ext --inplace
+2. Install in editable mode.
 
-4. Update ``$PYTHONPATH`` so that python knows where to find the local package
+   Editable mode is recommended for local development as it correctly links
+   the source files and compiled extensions.
 
    .. code-block:: shell
 
-      # Linux/Mac
-      export PYTHONPATH=<path_to_pyroomacoustics>:$PYTHONPATH
+         pip install -U -e .
 
-   For windows, see `this question <https://stackoverflow.com/questions/3701646/how-to-add-to-the-pythonpath-in-windows>`__
-   on stackoverflow.
+   The build process uses CMake to compile the C++ extensions. 
+   The ``-U`` flag ensures that the package is upgraded to the latest version.
+   Make sure to re-run this command when changing the C++ code.
 
-5. Install the dependencies listed in ``requirements.txt``
+   On macOS, if necessary, you can set the deployment target:
 
    .. code-block:: shell
 
-      pip install -r requirements.txt
+         MACOSX_DEPLOYMENT_TARGET=11.0 pip install -U -e .
 
-6. Now fire up ``python`` or ``ipython`` and check that the package can be
-   imported
+3. Verify the installation.
 
-   .. code-block:: python
+   .. code-block:: shell
 
-      import pyroomacoustics as pra
+      python -c "import pyroomacoustics as pra; print(pra.__version__)"
 
 Unit Tests
 ~~~~~~~~~~
 
 As much as possible, for every new function added to the code base, add
-a short test script in ``pyroomacoustics/tests``. The names of the
+a short test script in the top-level ``tests/`` directory. The names of the
 script and the functions running the test should be prefixed by
-``test_``. The tests are started by running ``nosetests`` at the root of
+``test_``. The tests are started by running ``pytest`` at the root of
 the package.
 
 How to make a clean pull request
@@ -167,18 +152,18 @@ How to deploy a new version to pypi
 
 1. git checkout pypi-release
 2. git merge master
-3. Change version number in ``pyroomacoustics/version.py`` to new version number vX.Y.Z
-4. Edit ``CHANGELOG.rst`` as follows
+3. Edit ``CHANGELOG.rst`` as follows
 
    - Add new title ``X.Y.Z_ - YEAR-MONTH-DAY`` under ``Unreleased``, add "Nothing yet" in the unreleased section.
-   - Edit appropriately the lists of links at the bottom of the file.
-5. git commit
-6. git tag vX.Y.Z
-7. git push origin vX.Y.Z
-8. git push
-9. git checkout master
-10. git merge pypi-release
-11. git push origin master
+   - Edit appropriately the list of links at the bottom of the file.
+4. git commit
+5. Tag the new version (e.g., vX.Y.Z). Version strings are automatically 
+   generated from git tags using `setuptools_scm`.
+6. git push origin vX.Y.Z
+7. git push
+8. git checkout master
+9. git merge pypi-release
+10. git push origin master
 
 Reference
 ---------

pyproject.toml

@@ -19,21 +19,27 @@ classifiers = [
     "Topic :: Scientific/Engineering :: Physics",
     "Topic :: Multimedia :: Sound/Audio :: Speech",
     "Topic :: Multimedia :: Sound/Audio :: Analysis",
-    "Programming Language :: Python :: 3.8",
     "Programming Language :: Python :: 3.9",
     "Programming Language :: Python :: 3.10",
     "Programming Language :: Python :: 3.11",
     "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
 ]
 dependencies = [
     "Cython",
     "numpy>=1.13.0",
     "scipy>=0.18.0",
 ]
-requires-python = ">=3.8"
+requires-python = ">=3.9"
 
 [project.urls]
 Homepage = "https://github.com/LCAV/pyroomacoustics"
+Repository = "https://github.com/LCAV/pyroomacoustics.git"
+Documentation = "https://pyroomacoustics.readthedocs.io/en/pypi-release/"
+Issues = "https://github.com/LCAV/pyroomacoustics/issues"
+Changelog = "https://github.com/LCAV/pyroomacoustics/blob/master/CHANGELOG.rst"
+
 
 [tool.setuptools.dynamic]
 readme = { file = ["README.rst"], content-type = "text/x-rst" }