meson-python 0.16.0__tar.gz → 0.17.0__tar.gz

{meson_python-0.16.0 → meson_python-0.17.0}/.cirrus.yml

@@ -47,12 +47,12 @@ fedora-37_task:
     cpu: 1
   << : *test
 
-manylinux-python3.11_task:
+manylinux-python3.13t_task:
   container:
     dockerfile: ci/manylinux.docker
     cpu: 1
   env:
-    PATH: "/opt/python/cp311-cp311/bin/:${PATH}"
+    PATH: "/opt/python/cp313-cp313t/bin/:${PATH}"
   << : *test
 
 manylinux-python3.7_task:
@@ -77,12 +77,12 @@ opensuse-15_task:
 
 freebsd_task:
   freebsd_instance:
-    image_family: freebsd-13-2
+    image_family: freebsd-14-0
   install_script: pkg install -y git ninja
   << : *test
 
 macos-arm64_task:
   macos_instance:
-    image: ghcr.io/cirruslabs/macos-ventura-xcode
+    image: ghcr.io/cirruslabs/macos-sonoma-xcode
   install_script: brew install git ninja python@3.11
   << : *test

{meson_python-0.16.0 → meson_python-0.17.0}/.github/workflows/docs.yml

@@ -31,10 +31,10 @@ jobs:
           python-version: '3.11'
       - uses: actions/checkout@v4
         with:
-          ref: ${{ github.event.push.tag || github.event.inputs.tag }}
+          ref: ${{ github.event.inputs.tag || github.ref }}
       - run: python -m pip install .[docs]
       - run: python -m sphinx -W docs/ build/docs/
-      - uses: actions/upload-pages-artifact@v2
+      - uses: actions/upload-pages-artifact@v3
         with:
           path: build/docs/
 
@@ -46,6 +46,6 @@ jobs:
     environment:
       name: github-pages
     runs-on: ubuntu-latest
-    if: ${{ github.event.push.tag || github.event.inputs.tag }}
+    if: ${{ github.event_name == 'workflow_dispatch' || github.ref_type == 'tag' }}
     steps:
-      - uses: actions/deploy-pages@v2
+      - uses: actions/deploy-pages@v4

{meson_python-0.16.0 → meson_python-0.17.0}/.github/workflows/tests.yml

@@ -36,58 +36,69 @@ concurrency:
 
 jobs:
   test:
-    runs-on: ${{ matrix.os }}-latest
+    runs-on: ${{ matrix.os }}
     strategy:
       fail-fast: false
       matrix:
         os:
-          - ubuntu
-          - macos
-          - windows
+          - ubuntu-latest
+          # actions/setup-python do not support Python 3.7 on macOS on
+          # arm64. The latest macOS version available is macOS 14 but
+          # it is arm64 only. Stick to macos-13 as long as we want to
+          # test Python 3.7 on macOS. macOS 14 on arm64 is covered by
+          # the Cirrus CI jobs.
+          - macos-13
+          - windows-latest
         python:
           - '3.7'
-          - '3.12'
+          - '3.13'
         meson:
           -
+        pyproject_metadata:
+          -
         include:
-          - os: ubuntu
+          - os: ubuntu-latest
             python: 'pypy-3.9'
-          - os: ubuntu
+          - os: ubuntu-latest
             python: 'pypy-3.10'
-          - os: ubuntu
+          - os: ubuntu-latest
             python: '3.8'
-          - os: ubuntu
+          - os: ubuntu-latest
             python: '3.9'
-          - os: ubuntu
+          - 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.
-          - os: ubuntu
+          - os: ubuntu-latest
             python: '3.11'
             meson: '~=0.63.3'
-          - os: ubuntu
+          - os: ubuntu-latest
             python: '3.11'
             meson: '~=0.64.0'
-          - os: ubuntu
+          - os: ubuntu-latest
             python: '3.11'
             meson: '~=1.0.0'
-          - os: ubuntu
+          - os: ubuntu-latest
             python: '3.11'
             meson: '~=1.1.0'
-          - os: ubuntu
+          - os: ubuntu-latest
             python: '3.12'
             meson: '~=1.2.3'
-          - os: ubuntu
+          - os: ubuntu-latest
             python: '3.12'
             meson: '~=1.3'
           # Test with Meson master branch.
-          - os: ubuntu
+          - os: ubuntu-latest
             python: '3.12'
             meson: '@git+https://github.com/mesonbuild/meson.git'
-          - os: windows
+          - os: windows-latest
             python: '3.12'
             meson: '@git+https://github.com/mesonbuild/meson.git'
+          # Test with oldest supported pyproject-metadata
+          - os: ubuntu-latest
+            python: '3.12'
+            pyproject_metadata: '==0.7.1'
 
     steps:
       - name: Checkout
@@ -100,30 +111,35 @@ jobs:
 
       - name: Install Ninja
         run: sudo apt-get install ninja-build
-        if: ${{ matrix.os == 'ubuntu' }}
+        if: ${{ runner.os == 'Linux' }}
 
       - name: Install Ninja
         run: brew install ninja
-        if: ${{ matrix.os == 'macos' }}
+        if: ${{ runner.os == 'macOS' }}
 
       - name: Install Ninja
         run: python -m pip install ninja
-        if: ${{ matrix.os == 'windows' }}
+        if: ${{ runner.os == 'Windows' }}
 
       - name: Install Meson
         run: python -m pip install "meson ${{ matrix.meson }}"
         if: ${{ matrix.meson }}
 
+      - name: Install pyproject-metadata
+        run: python -m pip install "pyproject-metadata ${{ matrix.pyproject_metadata }}"
+        if: ${{ matrix.pyproject_metadata }}
+
       - name: Install
         run: python -m pip install .[test]
 
       - name: Run tests
-        run: >-
-          python -m pytest --showlocals -vv --cov --cov-report=xml
+        run: python -m pytest --showlocals -vv --cov --cov-report=xml
 
       - name: Upload coverage report
         uses: codecov/codecov-action@v4
         if: ${{ always() }}
+        env:
+          CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
 
   msvc:
     runs-on: windows-latest
@@ -160,8 +176,7 @@ jobs:
         run: python -m pip install .[test]
 
       - name: Run tests
-        run: >-
-          python -m pytest --showlocals -vv
+        run: python -m pytest --showlocals -vv
 
   cygwin:
     runs-on: windows-latest
@@ -235,8 +250,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: Run tests
-        run: >-
-          python -m pytest --showlocals -vv
+        run: python -m pytest --showlocals -vv
         shell: C:\cygwin\bin\env.exe CYGWIN_NOWINPATH=1 CHERE_INVOKING=1 C:\cygwin\bin\bash.exe -leo pipefail -o igncr {0}
 
   pyston:
@@ -269,8 +283,7 @@ jobs:
         run: pyston -m pip install .[test]
 
       - name: Run tests
-        run: >-
-          pyston -m pytest --showlocals -vv
+        run: pyston -m pytest --showlocals -vv
 
   homebrew:
     runs-on: macos-latest
@@ -278,8 +291,8 @@ jobs:
       fail-fast: false
       matrix:
         python:
-          - '3.8'
-          - '3.11'
+          - '3.9'
+          - '3.12'
         meson:
           -
 
@@ -307,8 +320,7 @@ jobs:
         run: python -m pip install .[test]
 
       - name: Run tests
-        run: >-
-          python -m pytest --showlocals -vv
+        run: python -m pytest --showlocals -vv
 
   mypy:
     runs-on: ubuntu-latest

{meson_python-0.16.0 → meson_python-0.17.0}/.pre-commit-config.yaml

@@ -4,11 +4,12 @@
 
 ci:
   autofix_prs: false
-  autoupdate_commit_msg: 'MAINT: bump repositories'
+  autoupdate_commit_msg: 'MAINT: bump pre-commit dependencies'
+  autoupdate_schedule: 'quarterly'
 
 repos:
 - repo: https://github.com/pre-commit/pre-commit-hooks
-  rev: v4.5.0
+  rev: v5.0.0
   hooks:
   - id: check-ast
   - id: check-builtin-literals
@@ -21,12 +22,12 @@ repos:
   - id: end-of-file-fixer
   - id: trailing-whitespace
 - repo: https://github.com/astral-sh/ruff-pre-commit
-  rev: v0.1.5
+  rev: v0.6.9
   hooks:
   - id: ruff
     args: [--fix, --show-fixes, --output-format, grouped]
 - repo: https://github.com/fsfe/reuse-tool
-  rev: v2.1.0
+  rev: v4.0.3
   hooks:
   - id: reuse
     name: add SPDX headers

{meson_python-0.16.0 → meson_python-0.17.0}/CHANGELOG.rst

@@ -11,6 +11,32 @@
 Changelog
 +++++++++
 
+0.17.0
+======
+
+- Refuse to build wheels targeting the limited API and free-threaded CPython:
+  the free-threaded CPython build does not support the limited API yet.
+- Always use UTF-8 encoding for writing Meson native and cross files. Always
+  use UTF-8 encoding for reading read Meson introspection data and
+  ``pyproject.toml``.
+- Do not include uncommitted changes when creating source distributions.
+  Previously, uncommitted changes to files under version control were
+  included, but not untracked files. There was no strong use case for this
+  behavior and it was too surprising to keep it.
+- Make source distribution reproducible: use the modification time of
+  ``pyproject.toml`` for the generated files in the source distribution
+  archives.
+- Disable the ``abi3`` wheel tag for PyPy when building wheels targeting the
+  limited API: PyPy supports the limited API but not the stable ABI.
+- Raise ``ImportError`` when the package rebuild fails when importing an
+  editable install.
+- Fix the wheel platform tag for GraalPy.
+- Add ``.gitignore`` and ``.hgignore`` files to build directory if it is empty.
+- Allow ``install_subdir()`` of missing directories.
+
+Christian Clauss, Daniele Nicolodi, Jonathan J. Helmus, Leo Singer, Loïc
+Estève, Michael Simacek, Ralf Gommers, Simon McVittie --- 19-10-2024.
+
 0.16.0
 ======
 
@@ -38,7 +64,7 @@ Changelog
   emit a message indicating that the package is being rebuilt but
   suppress any output when there is no work to do.
 
-Daniele Nicolodi, Loïc Estève, Ralf Gommers  --- 16-04-2024
+Daniele Nicolodi, Loïc Estève, Ralf Gommers --- 16-04-2024
 
 
 0.15.0

{meson_python-0.16.0 → meson_python-0.17.0}/PKG-INFO

@@ -1,8 +1,8 @@
 Metadata-Version: 2.1
 Name: meson-python
-Version: 0.16.0
+Version: 0.17.0
 Summary: Meson Python build backend (PEP 517)
-Keywords: meson build backend pep517 package
+Keywords: meson,build,backend,pep517,package
 Home-page: https://github.com/mesonbuild/meson-python
 Maintainer-Email: Ralf Gommers <ralf.gommers@gmail.com>, Daniele Nicolodi <daniele@grinta.net>, Henry Schreiner <HenrySchreinerIII@gmail.com>, Thomas Li <47963215+lithomas1@users.noreply.github.com>
 License: Copyright © 2022 the meson-python contributors

meson_python-0.16.0/docs/contributing/release-process.rst → meson_python-0.17.0/RELEASE.rst

@@ -2,20 +2,16 @@
 ..
 .. SPDX-License-Identifier: MIT
 
-
-.. _contributing-release-process:
-
-***************
 Release Process
-***************
+===============
 
-All releases are PGP signed with one of the keys listed in the
-`installation page`_. Before releasing please make sure your PGP key is listed
-there, and preferably signed by one of the other key holders.
+All releases are PGP signed with one of the keys listed in ``docs/about.rst``.
+Before releasing please make sure your PGP key is listed there, and preferably
+signed by one of the other key holders.
 
-If your key is not signed by one of the other key holders, please make sure the
-PR that added your key to the :doc:`../about` page was approved by at least one
-other maintainer.
+If your key is not signed by one of the other key holders, please make sure
+that the PR that added your key to ``docs/about.rst`` was approved by at least
+one other maintainer.
 
 After that is done, you may release the project by following these steps:
 
@@ -44,7 +40,7 @@ After that is done, you may release the project by following these steps:
          $ git push
          $ git push --tags
 
-#. Release to `PyPI <https://pypi.org/project/meson-python/>`_
+#. Release to PyPI:
 
    #. Build the Python artifacts:
 
@@ -60,9 +56,3 @@ After that is done, you may release the project by following these steps:
 
       There is no need to GPG-sign the artifacts: PyPI no longer
       supports uploading GPG signatures.
-
-If you have any questions, please look at previous releases and/or ping the
-other maintainers.
-
-
-.. _installation page: installation

{meson_python-0.16.0 → meson_python-0.17.0}/ci/alpine-3.docker

@@ -2,6 +2,6 @@
 #
 # SPDX-License-Identifier: MIT
 
-# 20240305
+# 20240817
 FROM alpine:3
 RUN apk add --no-cache python3-dev py3-pip build-base ninja-is-really-ninja git patchelf

{meson_python-0.16.0 → meson_python-0.17.0}/ci/manylinux.docker

@@ -2,6 +2,6 @@
 #
 # SPDX-License-Identifier: MIT
 
-# 20221209
+# 20240513
 FROM quay.io/pypa/manylinux_2_28_x86_64
 RUN dnf -y update && dnf -y install ninja-build && dnf clean all

{meson_python-0.16.0 → meson_python-0.17.0}/ci/opensuse-15.docker

@@ -2,6 +2,6 @@
 #
 # SPDX-License-Identifier: MIT
 
-# 20230816
+# 20240817
 FROM opensuse/leap:latest
 RUN zypper --non-interactive install python311 python311-pip python311-devel gcc ninja git patchelf && zypper clean --all && ln -s python3.11 /usr/bin/python3

{meson_python-0.16.0 → meson_python-0.17.0}/docs/conf.py

@@ -16,15 +16,21 @@
 
 import datetime
 import os
+import time
 import sys
 sys.path.insert(0, os.path.abspath('..'))
 import mesonpy
 
+build_date = datetime.datetime.fromtimestamp(
+    int(os.environ.get('SOURCE_DATE_EPOCH', time.time())),
+    tz=datetime.timezone.utc,
+)
+
 
 # -- Project information -----------------------------------------------------
 
 project = 'meson-python'
-copyright = f'2021\N{EN DASH}{datetime.date.today().year} The meson-python developers'
+copyright = f'2021\N{EN DASH}{build_date.year} The meson-python developers'
 
 # The short X.Y version
 version = mesonpy.__version__

{meson_python-0.16.0 → meson_python-0.17.0}/docs/explanations/design-old.rst

@@ -31,21 +31,6 @@ Python tool (pip_, `pypa/build`_, etc.) to build and install the project.
 ``meson-python`` will build a Python sdist (source distribution) or
 wheel (binary distribution) from Meson_ project.
 
-Source distribution (sdist)
----------------------------
-
-The source distribution is based on ``meson dist``, so make sure all your files
-are included there. In git projects, Meson_ will not include files that are not
-checked into git, keep that in mind when developing. By default, all files
-under version control will be included in the sdist. In order to exclude files,
-use ``export-ignore`` or ``export-subst`` attributes in ``.gitattributes`` (see
-the ``git-archive`` documentation for details; ``meson dist`` uses
-``git-archive`` under the hood).
-
-Local (uncommitted) changes to files that are under version control will be
-included. This is often needed when applying patches, e.g. for build issues
-found during packaging, to work around test failures, to amend the license for
-vendored components in wheels, etc.
 
 Binary distribution (wheels)
 ----------------------------

meson_python-0.17.0/docs/how-to-guides/config-settings.rst

@@ -0,0 +1,128 @@
+.. SPDX-FileCopyrightText: 2023 The meson-python developers
+..
+.. SPDX-License-Identifier: MIT
+
+.. _how-to-guides-config-settings:
+
+***************************
+Using build config settings
+***************************
+
+Build config settings can be used to customize some aspects of the
+build. See the :doc:`../reference/config-settings` reference for a list
+of the settings implemented by ``meson-python``.
+
+How build config settings are specified depends on the Python package
+build front-end used. The most popular build front-end are `build`_ and
+`pip`_. These use the ``--config-settings`` long command line option or
+the ``-C`` short command line option:
+
+.. tab-set::
+
+    .. tab-item:: pypa/build
+        :sync: key_pypa_build
+
+	.. code-block:: console
+
+	   $ python -m build \
+               -Csetup-args="-Doption=true" \
+               -Csetup-args="-Dvalue=1" \
+               -Ccompile-args="-j6"
+
+    .. tab-item:: pip
+        :sync: key_pip
+
+	.. code-block:: console
+
+	   $ python -m pip wheel . \
+               --config-settings=setup-args="-Doption=disable" \
+               --config-settings=compile-args="-j6"
+
+
+Refer to the `build`_ and `pip`_ documentation for details.  This
+example uses the ``python -m pip wheel`` command to build a Python wheel
+that can be later installed or distributed. To build a package and
+immediately install it, replace ``wheel`` with ``install``.  See the
+:ref:`how-to-guides-meson-args` guide for more examples.
+
+
+.. admonition:: Passing multiple settings
+   :class: caution
+
+   Please note that ``pip`` prior to 23.1 did not offer a way to set a
+   build config setting to a list of strings: later values for the
+   same key passed to ``--config-settings`` override earlier ones,
+   effectively limiting the number of options that can be passed to
+   each command invoked in the build process to one. This limitation
+   has been lifted in ``pip`` release 23.1.
+
+
+.. _build: https://pypa-build.readthedocs.io/en/stable/
+.. _pip: https://pip.pypa.io/
+
+
+Using a persistent build directory
+==================================
+
+By default, ``meson-python`` uses a temporary build directory which is
+deleted when the build terminates. A persistent build directory allows
+faster incremental builds and to access build logs and intermediate
+build artifacts. The ``build-dir`` :ref:`config setting
+<reference-config-settings>` instructs ``meson-python`` to use a
+user-specified build directory which will not be deleted. For example:
+
+.. tab-set::
+
+    .. tab-item:: pypa/build
+        :sync: key_pypa_build
+
+	.. code-block:: console
+
+	   $ python -m build -Cbuild-dir=build
+
+    .. tab-item:: pip
+        :sync: key_pip
+
+	.. code-block:: console
+
+	   $ python -m pip install . -Cbuild-dir=build
+
+After running this command, the ``build`` directory will contain all
+the build artifacts and support files created by ``meson``, ``ninja``
+and ``meson-python``.  The same build directory can be used by
+subsequent invocations of ``meson-python``, avoiding the need to
+rebuild the whole project when testing changes during development.
+
+Using a permanent build directory also aids in debugging a failing
+build by allowing access to build logs and intermediate build outputs,
+including the Meson introspection files and detailed log. The latter
+is stored in the ``meson-logs/meson-log.txt`` file in the build
+directory and can be useful to diagnose why a build fails at the
+project configuration stage. For example, to understand why dependency
+detection failed, it is often necessary to look at the ``pkg-config``
+or other dependency detection methods output.
+
+Access to detailed logs and intermediate build outputs is particularly
+helpful in CI setups where introspecting the build environment is
+usually more difficult than on a local system. Therefore, it can be
+useful to show the more detailed log files when the CI build step
+fails. For example, the following GitHub Actions workflow file snippet
+shows the detailed Meson setup log when the build fails:
+
+.. code-block:: yaml
+
+    - name: Build the package
+      run: python -m build --wheel -Cbuild-dir=build
+    - name: Show meson-log.txt
+      if: failure()
+      run: cat build/meson-logs/meson-log.txt
+
+Replacing ``failure()`` with ``always()`` in the code above will
+result in the Meson log file always being shown. See the GitHub
+Actions documentation__ for more details. Please be aware that the
+setup log can become very long for complex projects, and the GitHub
+Actions web interface becomes unresponsive when the running job emits
+many output lines.
+
+
+__ https://docs.github.com/en/actions/learn-github-actions/expressions#status-check-functions

meson_python-0.17.0/docs/how-to-guides/sdist.rst

@@ -0,0 +1,54 @@
+.. SPDX-FileCopyrightText: 2024 The meson-python developers
+..
+.. SPDX-License-Identifier: MIT
+
+.. _sdist:
+
+******************************
+Creating a source distribution
+******************************
+
+A source distribution for the project can be created executing
+
+.. code-block:: console
+
+   $ python -m build --sdist .
+
+in the project root folder. This will create a ``.tar.gz`` archive in the
+``dist`` folder in the project root folder. This archive contains the full
+contents of the latest commit in revision control with all revision control
+metadata removed. Uncommitted modifications and files unknown to the revision
+control system are not included.
+
+The source distribution archive is created by adding the required metadata
+files to the archive obtained by executing the ``meson dist --no-tests
+--allow-dirty`` command. To generate a source distribution, ``meson-python``
+must successfully configure the Meson project by running the ``meson setup``
+command. Additional arguments can be passed to ``meson dist`` to alter its
+behavior. Refer to the relevant `Meson documentation`__ and to the
+:ref:`how-to-guides-meson-args` guide for details.
+
+The ``meson dist`` command uses the archival tool of the underlying revision
+control system for creating the archive. This implies that a source
+distribution can only be created for a project versioned in a revision control
+system. Meson supports the Git and Mercurial revision control systems.
+
+Files can be excluded from the source distribution via the relevant mechanism
+provided by the revision control system. When using Git as a revision control
+system, it is possible to exclude files from the source distribution setting
+the ``export-ignore`` attribute. For example, adding a ``.gitattributes``
+files containing
+
+.. code-block:: none
+
+   dev/** export-ignore
+
+would result in the ``dev`` folder to be excluded from the source
+distribution. Refer to the ``git archive`` documentation__ for
+details. Another mechanism to alter the content of the source distribution is
+offered by dist scripts. Refer to the relevant `Meson documentation`__ for
+details.
+
+__ https://mesonbuild.com/Creating-releases.html
+__ https://git-scm.com/docs/git-archive#ATTRIBUTES
+__ https://mesonbuild.com/Reference-manual_builtin_meson.html#mesonadd_dist_script

{meson_python-0.16.0 → meson_python-0.17.0}/docs/index.rst

@@ -77,6 +77,7 @@ the use of ``meson-python`` and Meson for Python packaging.
    :hidden:
 
    tutorials/introduction
+   how-to-guides/sdist
    how-to-guides/editable-installs
    how-to-guides/config-settings
    how-to-guides/meson-args
@@ -100,7 +101,6 @@ the use of ``meson-python`` and Meson for Python packaging.
 
    changelog
    about
-   contributing/index
    Discussions <https://github.com/mesonbuild/meson-python/discussions>
    Source Code <https://github.com/mesonbuild/meson-python>
    Issue Tracker <https://github.com/mesonbuild/meson-python/issues>

{meson_python-0.16.0 → meson_python-0.17.0}/docs/reference/config-settings.rst

@@ -23,10 +23,6 @@ them.
    exists and contains a valid Meson build directory setup, the
    project will be reconfigured using ``meson setup --reconfigure``.
 
-   The same build directory can be used by subsequent invocations of
-   ``meson-python``. This avoids having to rebuild the whole project
-   when testing changes during development.
-
    For backward compatibility reasons, the alternative ``builddir``
    spelling is also accepted.
 

{meson_python-0.16.0 → meson_python-0.17.0}/docs/tutorials/introduction.rst

@@ -255,6 +255,19 @@ If the build succeeded, you'll have the binary artifacts in the ``dist`` folder.
    easier, we recommend checking out the cibuildwheel_ project, which allows you
    to automate it.
 
+Build isolation
+```````````````
+
+Building with ``python -m build`` or with ``pip`` uses build isolation by
+default. I.e., the build frontend creates a new, temporary virtual environment
+with all build dependencies before calling ``meson-python`` to build a wheel.
+
+If you disable build isolation, you are responsible for ensuring that
+``meson-python`` and all other build dependencies for the package are installed
+already in the Python environment. Note that if you use a virtual environment
+to build in, it must be activated (otherwise ``meson`` or another executable
+may not be found).
+
 
 Distributing the project
 ------------------------

{meson_python-0.16.0 → meson_python-0.17.0}/meson.build

@@ -2,7 +2,7 @@
 #
 # SPDX-License-Identifier: MIT
 
-project('meson-python', version: '0.16.0')
+project('meson-python', version: '0.17.0')
 
 py = import('python').find_installation()