meson-python 0.21.1__tar.gz → 0.22.0__tar.gz

{meson_python-0.21.1 → meson_python-0.22.0}/.github/workflows/tests.yml

@@ -49,19 +49,15 @@ jobs:
           # a job running on macOS on x86-64 for a while longer.
           - macos-15-intel
         python:
-          - '3.9'
+          - '3.10'
           - '3.15'
         meson:
           -
         dependencies:
           -
         include:
-          - os: ubuntu-latest
-            python: 'pypy-3.9'
           - os: ubuntu-latest
             python: 'pypy-3.11'
-          - os: ubuntu-latest
-            python: '3.10'
           # Test with older supported Meson version.  Meson up to
           # version 1.2.3 requires distutils, which has been removed
           # from the stdlib in Python 3.12, thus test with Pythn 3.11.
@@ -100,6 +96,15 @@ jobs:
           - os: ubuntu-latest
             python: '3.13'
             meson: '~=1.8.0'
+          - os: ubuntu-latest
+            python: '3.13'
+            meson: '~=1.9.0'
+          - os: ubuntu-latest
+            python: '3.13'
+            meson: '~=1.10.0'
+          - os: ubuntu-latest
+            python: '3.13'
+            meson: '~=1.11.0'
           # Test with Meson master branch.
           - os: ubuntu-latest
             python: '3.14'
@@ -205,7 +210,7 @@ jobs:
       fail-fast: false
       matrix:
         python:
-          - '3.9'
+          - '3.12'
         meson:
           -
 
@@ -219,10 +224,11 @@ jobs:
         uses: cygwin/cygwin-install-action@3f0a3f9f988f7e96b8c18098ae05eaec175f5b52  # v6
         with:
           packages: >-
-            python39
-            python39-devel
-            python39-pip
-            python39-setuptools
+            python312
+            python312-devel
+            python312-pip
+            python312-setuptools
+            python312-virtualenv
             cmake
             gcc-core
             gcc-g++
@@ -261,16 +267,7 @@ jobs:
         shell: C:\cygwin\bin\env.exe CYGWIN_NOWINPATH=1 CHERE_INVOKING=1 C:\cygwin\bin\bash.exe -leo pipefail -o igncr {0}
 
       - name: Install
-        # Cygwin patches Python's ensurepip module to look for the
-        # wheels needed to initialize a new virtual environment in
-        # /usr/share/python-wheels/ but nothing in Cygwin actually
-        # puts the setuptools and pip wheels there. Fix this.
-        run: |
-          mkdir /usr/share/python-wheels/
-          pushd /usr/share/python-wheels/
-          python -m pip download setuptools pip
-          popd
-          python -m pip install . --group test
+        run: python -m pip install . --group test
         shell: C:\cygwin\bin\env.exe CYGWIN_NOWINPATH=1 CHERE_INVOKING=1 C:\cygwin\bin\bash.exe -leo pipefail -o igncr {0}
 
       - name: Run tests
@@ -283,7 +280,7 @@ jobs:
       fail-fast: false
       matrix:
         python:
-          - '3.9'
+          - '3.10'
           - '3.12'
         meson:
           -
@@ -327,13 +324,13 @@ jobs:
       - name: Setup Python
         uses: actions/setup-python@v7
         with:
-          python-version: 3.9
+          python-version: '3.10'
 
       - name: Install dependencies
         run: python -m pip install .
 
       - name: Install mypy
-        run: python -m pip install mypy~=1.19
+        run: python -m pip install mypy~=2.3.1
 
       - name: Run mypy
         run: mypy -p mesonpy
@@ -355,3 +352,19 @@ jobs:
       - name: Run tests
         working-directory: .github/workflows
         run: pixi run test
+
+  uv-sync:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@bec219d24cd3e171d82865faccec33120bb574f4 # v10.1.0
+        with:
+          enable-cache: false
+          version: "0.12.13"  # Released on 2026-09-10
+
+      # Ensure that dependencies and dependency groups are consistent and resolvable.
+      - run: uv sync --all-extras --all-groups --dry-run

{meson_python-0.21.1 → meson_python-0.22.0}/.gitignore

@@ -10,3 +10,4 @@ docs/_build
 dist/
 .coverage
 tests/packages/**/.wraplock
+*.lock

{meson_python-0.21.1 → meson_python-0.22.0}/.pre-commit-config.yaml

@@ -2,6 +2,8 @@
 #
 # SPDX-License-Identifier: MIT
 
+# 'pre-commit' is not a project dependency -- if needed, users may choose to install it
+
 ci:
   autofix_prs: false
   autoupdate_commit_msg: 'MAINT: bump pre-commit dependencies'

{meson_python-0.21.1 → meson_python-0.22.0}/CHANGELOG.rst

@@ -11,6 +11,19 @@
 Changelog
 +++++++++
 
+0.22.0
+======
+
+- Add support for adding RPATH entries specified with ``install_rpath``
+  argument to Meson functions that accept it.
+- Add support for removing build RPATH entries added by Meson to allow
+  executing parts of the project from the build directory.
+- Fix corner cases in handling RPATH entries and relocation of shared
+  libraries distributed as part of Python packages.
+
+Daniele Nicolodi, Mike Taves, Nathan Goldbaum, Ralf Gommers --- 25-09-2026.
+
+
 0.21.1
 ======
 
@@ -30,8 +43,9 @@ Daniele Nicolodi, Ralf Gommers --- 11-09-2026.
   build errors when rebuilding.
 - Use ``.start`` files (PEP 829) instead of ``.pth`` files to implement editable
   wheels for Python 3.15 and later.
+- From this release onwards, SSH keys used to sign release tags.
 
-Daniele Nicolodi, Michał Górny, Ralf Gommers --- 25-08-2026.
+Daniele Nicolodi, Michał Górny, Ralf Gommers --- 07-09-2026.
 
 
 0.20.0

{meson_python-0.21.1 → meson_python-0.22.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: meson-python
-Version: 0.21.1
+Version: 0.22.0
 Summary: The Python build backend for Meson projects
 Keywords: meson,build,backend,pep517,package
 Maintainer-Email: Ralf Gommers <ralf.gommers@gmail.com>, Daniele Nicolodi <daniele@grinta.net>, Henry Schreiner <HenrySchreinerIII@gmail.com>
@@ -13,7 +13,7 @@ Project-URL: homepage, https://github.com/mesonbuild/meson-python
 Project-URL: repository, https://github.com/mesonbuild/meson-python
 Project-URL: documentation, https://mesonbuild.com/meson-python/
 Project-URL: changelog, https://mesonbuild.com/meson-python/changelog.html
-Requires-Python: >=3.9
+Requires-Python: >=3.10
 Requires-Dist: meson>=0.64.0; python_version < "3.12"
 Requires-Dist: meson>=1.2.3; python_version >= "3.12"
 Requires-Dist: packaging>=23.2; sys_platform != "ios"

meson_python-0.22.0/RELEASE.rst

@@ -0,0 +1,49 @@
+.. SPDX-FileCopyrightText: 2023 The meson-python developers
+..
+.. SPDX-License-Identifier: MIT
+
+Release Process
+===============
+
+Releases are published as git tags, signed with either an SSH or a PGP key
+belonging to a maintainer. The signing key must be registered on GitHub so that
+GitHub shows the tag as verified.
+
+You may release the project by following these steps:
+
+#. Release to the Git repository on GitHub:
+
+   #. Create the release commit
+
+      #. Bump the versions in ``pyproject.toml`` and in ``mesonpy/__init__.py``.
+      #. Create ``CHANGELOG.rst`` section for the new release and fill it.
+      #. The commit message should read: ``REL: set version to X.Y.Z``
+
+   #. Create a signed tag for the release:
+
+      .. code-block:: console
+
+         $ git tag -s X.Y.Z
+
+      This signs with your PGP key by default. To sign with an SSH key instead,
+      configure git once beforehand:
+
+      .. code-block:: console
+
+         $ git config --global gpg.format ssh
+         $ git config --global user.signingkey ~/.ssh/id_ed25519.pub
+
+      The SSH signing key must be registered on
+      GitHub as a Signing Key for the tag to show as verified.
+
+      The tag title should follow the ``meson-python X.Y.Z`` format, and the
+      tag body should be a plain text version of the change-log for the current
+      release.
+
+   #. Push the tag to the repository:
+
+      .. code-block:: console
+
+         $ git push --tags
+
+#. Release to PyPI is done via trusted publishing, triggering on the tag.

{meson_python-0.21.1 → meson_python-0.22.0}/docs/about.rst

@@ -49,13 +49,20 @@ supported Python versions.
 
 Distributors are recommended to fetch release sources from the
 corresponding tags on the Git repository_ or from source distributions
-on `PyPI`_. Git tags are PGP-signed with one of the following keys:
+on `PyPI`_. From ``0.21.0`` onwards, releases are published as signed tags,
+signed with either an SSH or a PGP key belonging to `@rgommers`_ or
+`@dnicolodi`_. Those signing keys can be retrieved from GitHub.
+
+Releases up to and including ``0.20.0`` are PGP-signed with one of the
+following keys:
 
 - |3DCE51D60930EBA47858BA4146F633CBB0EB4BF2|_ Filipe Laíns
 - |52BDC33FD1FBAB569D47FFA923D9E5499A08BDC5|_ Ralf Gommers
 
 .. _repository: https://github.com/mesonbuild/meson-python
 .. _PyPI: https://pypi.org/project/meson-python/
+.. _@rgommers: https://github.com/rgommers
+.. _@dnicolodi: https://github.com/dnicolodi
 
 .. |3DCE51D60930EBA47858BA4146F633CBB0EB4BF2| replace:: ``3DCE51D60930EBA47858BA4146F633CBB0EB4BF2``
 .. _3DCE51D60930EBA47858BA4146F633CBB0EB4BF2: https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x3dce51d60930eba47858ba4146f633cbb0eb4bf2

{meson_python-0.21.1 → meson_python-0.22.0}/docs/changelog.rst

@@ -11,6 +11,19 @@
 Changelog
 +++++++++
 
+0.22.0
+======
+
+- Add support for adding RPATH entries specified with ``install_rpath``
+  argument to Meson functions that accept it.
+- Add support for removing build RPATH entries added by Meson to allow
+  executing parts of the project from the build directory.
+- Fix corner cases in handling RPATH entries and relocation of shared
+  libraries distributed as part of Python packages.
+
+Daniele Nicolodi, Mike Taves, Nathan Goldbaum, Ralf Gommers --- 25-09-2026.
+
+
 0.21.1
 ======
 
@@ -30,8 +43,9 @@ Daniele Nicolodi, Ralf Gommers --- 11-09-2026.
   build errors when rebuilding.
 - Use ``.start`` files (PEP 829) instead of ``.pth`` files to implement editable
   wheels for Python 3.15 and later.
+- From this release onwards, SSH keys used to sign release tags.
 
-Daniele Nicolodi, Michał Górny, Ralf Gommers --- 25-08-2026.
+Daniele Nicolodi, Michał Górny, Ralf Gommers --- 07-09-2026.
 
 
 0.20.0

meson_python-0.22.0/docs/how-to-guides/limited-api.rst

@@ -0,0 +1,176 @@
+.. SPDX-FileCopyrightText: 2026 The meson-python developers
+..
+.. SPDX-License-Identifier: MIT
+
+.. _howto-limited-api:
+
+***********************************
+Targeting the CPython Limited C API
+***********************************
+
+This page describes how to configure your package to build against the
+CPython `limited API`_ and build `stable ABI`_ wheels. Limited API builds
+target a minimum interpreter version and produce a single wheel that
+can support newer interpreter versions.
+
+You can enable limited API builds by default or make them opt-in.
+We recommend making them opt-in to avoid failures or special handling
+when building for interpreters that do not support the stable ABI, such
+as free-threaded CPython 3.14. Using the version-specific C API can also
+`improve performance`_ for source installations and distribution packages
+that do not need the stable ABI.
+
+Compile your extension modules for the limited API by specifying the
+``limited_api`` argument to the ``extension_module()`` function in the
+Meson Python module. The version passed to ``limited_api`` selects
+the limited API your extension uses. Meson converts this version to
+the corresponding value of the ``Py_LIMITED_API`` preprocessor macro.
+
+The wheel's :ref:`Python compatibility tag <limited-api-wheel-tags>`
+still corresponds to the interpreter used for the build, regardless of
+the ``limited_api`` version you select.
+
+Enabling the
+:option:`tool.meson-python.limited-api` setting declares that all the
+extension modules in your package target the limited API and adjusts the
+wheel filename ABI tag accordingly:
+
+.. code-block:: meson
+
+   py = import('python').find_installation(pure: false)
+
+   py.extension_module(
+       '_core',
+       '_core.c',
+       limited_api: '3.10',
+       install: true,
+       subdir: 'example',
+   )
+
+.. code-block:: toml
+
+   [tool.meson-python]
+   limited-api = true
+
+
+For limited API builds, on platforms where Python extension modules
+targeting the stable ABI use a dedicated filename suffix, ``meson-python``
+verifies that all the extension modules included in the wheel use the
+stable ABI filename suffix and fails the build otherwise.
+
+
+.. _opt-in-limited-api-example:
+
+Set up Limited API support as opt-in
+------------------------------------
+
+To make limited API builds opt-in, add
+``python.allow_limited_api=false`` to the ``default_options`` in your
+existing ``project()`` call in ``meson.build``:
+
+.. code-block:: meson
+
+   project(
+       'example',
+       'c',
+       default_options: ['python.allow_limited_api=false'],
+   )
+
+Keep ``limited-api = true`` in ``pyproject.toml`` and the ``limited_api``
+argument to ``extension_module()`` as shown above. When
+``python.allow_limited_api`` is false, Meson ignores the ``limited_api``
+argument, compiles extension modules for the ABI of the interpreter
+used for the build, and produces a wheel tagged as compatible with
+the build interpreter.
+
+To build a stable ABI wheel, explicitly enable limited API builds:
+
+.. tab-set::
+
+   .. tab-item:: pypa/build
+      :sync: key_pypa_build
+
+      .. code-block:: console
+
+         $ python -m build --wheel -Csetup-args="-Dpython.allow_limited_api=true" .
+
+   .. tab-item:: pip
+      :sync: key_pip
+
+      .. code-block:: console
+
+         $ python -m pip wheel -Csetup-args="-Dpython.allow_limited_api=true" .
+
+
+.. _limited-api-wheel-tags:
+
+Limited API compatibility
+-------------------------
+
+``meson-python`` conservatively chooses the wheel's Python compatibility
+tag based only on the interpreter used for the build, regardless of the
+target ``limited_api`` version.  For example, a wheel built with CPython
+3.12 for the 3.10 limited API is tagged ``cp312-abi3`` and can be
+installed only on GIL-enabled CPython 3.12 and later. When building
+stable ABI wheels for distribution, for example on PyPI, build with the
+oldest CPython version you want the wheel to support, as `recommended by
+CPython`_.  If you are installing from source into a particular
+environment, use that environment's interpreter; you do not need to
+build with the oldest supported version.
+
+PyPy supports the limited API, but does not implement a stable ABI, thus
+the :option:`tool.meson-python.limited-api` setting has no effect on the
+wheel tags when building with PyPy.
+
+
+The ``abi3t`` stable ABI
+------------------------
+
+CPython 3.15 introduces the ``abi3t`` stable ABI. Extension modules built
+for ``abi3t`` can be loaded by both the GIL-enabled and the free-threaded
+builds of CPython 3.15 and later: a single wheel tagged ``abi3.abi3t``
+supports all CPython interpreters from version 3.15 on.
+
+``abi3t`` extension modules require limited API version 3.15 or later
+and, currently, a free-threaded interpreter for the build: compiling
+for ``abi3t`` with a GIL-enabled interpreter is not supported yet.
+Once you have made the source changes described in the
+`abi3t migration guide`_, no additional build configuration is required:
+the CPython headers select ``abi3t`` when ``Py_LIMITED_API`` is defined
+while compiling for a free-threaded interpreter.
+
+Meson refuses a ``limited_api`` version newer than the interpreter
+used for the build.  If you build ``abi3`` wheels for older
+CPython versions and ``abi3.abi3t`` wheels for CPython 3.15 and later,
+you can select the limited API version by querying the ``Py_GIL_DISABLED``
+sysconfig variable, which is 1 for free-threaded builds:
+
+.. code-block:: meson
+
+   py = import('python').find_installation(pure: false)
+
+   limited_api = '3.10'
+   if py.language_version().version_compare('>=3.15')
+       if py.get_variable('Py_GIL_DISABLED') == 1
+           limited_api = '3.15'
+       endif
+   endif
+
+   py.extension_module(
+       '_core',
+       '_core.c',
+       limited_api: limited_api,
+       install: true,
+       subdir: 'example',
+   )
+
+Free-threaded CPython 3.13 and 3.14 do not support the limited API:
+disable limited API builds when using these interpreters.
+The :ref:`opt-in configuration above <opt-in-limited-api-example>`
+disables them by default.
+
+.. _limited API: https://docs.python.org/3/c-api/stable.html#limited-c-api
+.. _stable ABI: https://docs.python.org/3/c-api/stable.html#stable-application-binary-interface
+.. _recommended by CPython: https://docs.python.org/3/c-api/stable.html#limited-api-caveats
+.. _improve performance: https://docs.python.org/3/c-api/stable.html#limited-api-scope-and-performance
+.. _abi3t migration guide: https://docs.python.org/3.15/howto/abi3t-migration.html

{meson_python-0.21.1 → meson_python-0.22.0}/docs/how-to-guides/shared-libraries.rst

@@ -67,11 +67,7 @@ is to be used inside the Python package being built, then it is best to modify
 the install location, via the ``install_dir`` argument, to be within
 the Python package itself:
 
-.. TODO update the text block below to 'meson' when
-.. meson lexer is updated to fix
-.. https://github.com/pygments/pygments/issues/2918
-
-.. code-block:: text
+.. code-block:: meson
 
     example_lib = shared_library(
         'example',
@@ -80,8 +76,9 @@ the Python package itself:
         install_dir: py.get_install_dir() / 'mypkg/subdir',
     )
 
-Then an extension module in the same install directory can link against the
-shared library in a portable manner by using ``install_rpath``:
+On Linux, macOS, and in general on all systems except Windows, an extension
+module can dynamically link against a shared library installed in the same
+package by using ``install_rpath`` with a relative path:
 
 .. code-block:: meson
 
@@ -90,12 +87,17 @@ shared library in a portable manner by using ``install_rpath``:
         link_with: example_lib,
         install: true,
         subdir: 'mypkg/subdir',
-        install_rpath: '$ORIGIN'
+        install_rpath: host_machine.system() == 'darwin' ? '@loader_path' : '$ORIGIN'
     )
 
-The above method will work as advertised on macOS and Linux; ``meson-python`` does
-nothing special for this case. Windows needs some special handling though, due to
-the lack of RPATH support:
+Note that Mach-O binaries on macOS use the ``@loader_path`` token to indicate
+the location of the current executable or shared library while ELF binaries use
+the ``$ORIGIN`` token.  For backward compatibility, ``meson-python`` translates
+the more common ``$ORIGIN`` token to the macOS-specific ``@loader_path`` token
+when building on macOS. However, Meson itself does not, thus relying on this
+translation is discouraged.
+
+Windows needs some special handling though, due to the lack of RPATH support:
 
 .. literalinclude:: ../../tests/packages/sharedlib-in-package/mypkg/__init__.py
    :start-after: start-literalinclude

{meson_python-0.21.1 → meson_python-0.22.0}/docs/index.rst

@@ -55,7 +55,8 @@ can be overridden and extended using the standard package metadata format in the
    version = '1.0.0'
    description = 'Example package using the meson-python build backend'
    readme = 'README.rst'
-   license = {file = 'LICENSE.txt'}
+   license = 'MIT'
+   license-files = ['LICENSE.txt']
    authors = [
      {name = 'Au Thor', email = 'author@example.com'},
    ]
@@ -83,6 +84,7 @@ the use of ``meson-python`` and Meson for Python packaging.
    how-to-guides/meson-args
    how-to-guides/debug-builds
    how-to-guides/shared-libraries
+   how-to-guides/limited-api
    reference/limitations
    projects-using-meson-python
 

{meson_python-0.21.1 → meson_python-0.22.0}/docs/reference/meson-compatibility.rst

@@ -52,10 +52,20 @@ versions.
    populate the package license and license files from the ones
    declared via the ``project()`` call in ``meson.build``.
 
+   Meson 1.6.0 or later is also required to support the
+   ``install_rpath`` argument to Meson functions that accept it, such
+   as ``library()`` and ``extension_module()``.  On older Meson
+   versions, this argument has no effect.
+
 .. option:: 1.9.0
 
    Meson 1.9.0 or later is required to support building for iOS.
 
+   Meson 1.9.0 or later is also required to remove RPATH entries that
+   are added by Meson to allow executing parts of the project from
+   the build directory and that are normally removed during ``meson
+   install``. On older Meson versions, these entries are not removed.
+
 Build front-ends by default build packages in an isolated Python
 environment where build dependencies are installed. Most often, unless
 a package or its build dependencies declare explicitly a version

{meson_python-0.21.1 → meson_python-0.22.0}/docs/reference/pyproject-settings.rst

@@ -40,11 +40,12 @@ use them and examples.
    modules can be compiled for the Python limited API specifying the
    ``limited_api`` argument to the |extension_module()|_ function
    in the Meson Python module.  When this setting is set to true, the
-   value ``abi3`` is used for the Python wheel filename ABI tag.
-
-   This setting is automatically reverted to false when the
+   Python wheel filename ABI tag is set to ``abi3``, or ``abi3.abi3t``
+   when building with free-threaded CPython 3.15 or later.  This
+   setting is automatically reverted to false when the
    ``-Dpython.allow_limited_api=false`` option is passed to ``meson
-   setup``.
+   setup``. See :ref:`howto-limited-api` for more information on limited
+   API builds.
 
 .. option:: tool.meson-python.meson
 
@@ -98,7 +99,7 @@ use them and examples.
    glob pattern is useful exclusively to limit the effect of an exclude
    pattern that matches too many files.
 
-.. _python limited api: https://docs.python.org/3/c-api/stable.html?highlight=limited%20api#stable-application-binary-interface
+.. _python limited api: https://docs.python.org/3/c-api/stable.html#stable-application-binary-interface
 .. _extension_module(): `https://mesonbuild.com/Python-module.html#extension_module
 .. _meson introspection data: https://mesonbuild.com/IDE-integration.html#install-plan
 

{meson_python-0.21.1 → meson_python-0.22.0}/docs/tutorials/introduction.rst

@@ -139,7 +139,8 @@ self-explanatory:
    description = 'Our first Python project, using meson-python!'
    readme = 'README.md'
    requires-python = '>=3.8'
-   license = {file = 'LICENSE.txt'}
+   license = 'MIT'
+   license-files = ['LICENSE.txt']
    authors = [
      {name = 'Bowsette Koopa', email = 'bowsette@example.com'},
    ]