Latest setuptools and flit now support PEP 639

This updates the now outdated notes added in
faf4c7d.

Closes #1831.

Author: not-my-profile

source/guides/licensing-examples-and-user-scenarios.rst

@@ -12,8 +12,6 @@ This document aims to provide clear guidance how to migrate from the legacy
 to the standardized way of declaring licenses.
 Make sure your preferred build backend supports :pep:`639` before
 trying to apply the newer guidelines.
-As of February 2025, :doc:`setuptools <setuptools:userguide/pyproject_config>`
-and :ref:`flit <flit:pyproject_toml_project>` don't support :pep:`639` yet.
 
 
 Licensing Examples

source/guides/writing-pyproject-toml.rst

@@ -328,10 +328,11 @@ You can also specify the format explicitly, like this:
 -----------
 
 :pep:`639` (accepted in August 2024) has changed the way the ``license`` field
-is declared. Make sure your preferred build backend supports :pep:`639` before
-trying to apply the newer guidelines.
-As of February 2025, :doc:`setuptools <setuptools:userguide/pyproject_config>`
-and :ref:`flit <flit:pyproject_toml_project>` don't support :pep:`639` yet.
+is declared. As of February 19th 2025 the latest versions of all recommended
+build backends support :pep:`639` (although :ref:`flit <flit:pyproject_toml_project>`
+only supports single license expressions as of flit 3.11.0)
+If you have to use an older version of a build backend, that doesn't support it
+yet, you have to use the legacy format instead.
 
 :pep:`639` license declaration
 ''''''''''''''''''''''''''''''
@@ -394,10 +395,6 @@ whose license is unapproved.)
 -----------------
 
 :pep:`639` (accepted in August 2024) has introduced the ``license-files`` field.
-Make sure your preferred build backend supports :pep:`639` before declaring the
-field.
-As of February 2025, :doc:`setuptools <setuptools:userguide/pyproject_config>`
-and :ref:`flit <flit:pyproject_toml_project>` don't support :pep:`639` yet.
 
 This is a list of license files and files containing other legal
 information you want to distribute with your package.

source/tutorials/packaging-projects.rst

@@ -141,31 +141,31 @@ for more details.
     .. code-block:: toml
 
         [build-system]
-        requires = ["hatchling"]
+        requires = ["hatchling>=1.26"]
         build-backend = "hatchling.build"
 
 .. tab:: setuptools
 
     .. code-block:: toml
 
         [build-system]
-        requires = ["setuptools>=61.0"]
+        requires = ["setuptools>=77.0.1"]
         build-backend = "setuptools.build_meta"
 
 .. tab:: Flit
 
     .. code-block:: toml
 
         [build-system]
-        requires = ["flit_core>=3.4"]
+        requires = ["flit_core>=3.11.0"]
         build-backend = "flit_core.buildapi"
 
 .. tab:: PDM
 
     .. code-block:: toml
 
         [build-system]
-        requires = ["pdm-backend"]
+        requires = ["pdm-backend>=2.4.0"]
         build-backend = "pdm.backend"
 
 
@@ -175,6 +175,9 @@ Frontends usually run builds in isolated environments, so omitting dependencies
 here may cause build-time errors.
 This should always include your backend's package, and might have other build-time
 dependencies.
+The minimum version specified in the above code block is the one that introduced support
+for `license-files` being a list, if you need to use an older version you can adapt
+this requirement but will also need to specify the license files in a legacy format.
 
 The ``build-backend`` key is the name of the Python object that frontends will use
 to perform the build.
@@ -200,52 +203,27 @@ to include your username; this ensures that you have a unique
 package name that doesn't conflict with packages uploaded by other people
 following this tutorial.
 
-.. tab:: hatchling/pdm
-
-  .. code-block:: toml
-
-      [project]
-      name = "example_package_YOUR_USERNAME_HERE"
-      version = "0.0.1"
-      authors = [
-        { name="Example Author", email="[email protected]" },
-      ]
-      description = "A small example package"
-      readme = "README.md"
-      requires-python = ">=3.8"
-      classifiers = [
-          "Programming Language :: Python :: 3",
-          "Operating System :: OS Independent",
-      ]
-      license = "MIT"
-      license-files = ["LICEN[CS]E*"]
-
-      [project.urls]
-      Homepage = "https://github.com/pypa/sampleproject"
-      Issues = "https://github.com/pypa/sampleproject/issues"
-
-.. tab:: setuptools/flit
-
-  .. code-block:: toml
-
-      [project]
-      name = "example_package_YOUR_USERNAME_HERE"
-      version = "0.0.1"
-      authors = [
-        { name="Example Author", email="[email protected]" },
-      ]
-      description = "A small example package"
-      readme = "README.md"
-      requires-python = ">=3.8"
-      classifiers = [
-          "Programming Language :: Python :: 3",
-          "Operating System :: OS Independent",
-          "License :: OSI Approved :: MIT License",
-      ]
-
-      [project.urls]
-      Homepage = "https://github.com/pypa/sampleproject"
-      Issues = "https://github.com/pypa/sampleproject/issues"
+.. code-block:: toml
+
+    [project]
+    name = "example_package_YOUR_USERNAME_HERE"
+    version = "0.0.1"
+    authors = [
+      { name="Example Author", email="[email protected]" },
+    ]
+    description = "A small example package"
+    readme = "README.md"
+    requires-python = ">=3.8"
+    classifiers = [
+        "Programming Language :: Python :: 3",
+        "Operating System :: OS Independent",
+    ]
+    license = "MIT"
+    license-files = ["LICEN[CS]E*"]
+
+    [project.urls]
+    Homepage = "https://github.com/pypa/sampleproject"
+    Issues = "https://github.com/pypa/sampleproject/issues"
 
 - ``name`` is the *distribution name* of your package. This can be any name as
   long as it only contains letters, numbers, ``.``, ``_`` , and ``-``. It also
@@ -274,10 +252,9 @@ following this tutorial.
   your package will work on. For a complete list of classifiers, see
   https://pypi.org/classifiers/.
 - ``license`` is the :term:`SPDX license expression <License Expression>` of
-  your package. Not supported by all the build backends yet.
+  your package.
 - ``license-files`` is the list of glob paths to the license files,
   relative to the directory where :file:`pyproject.toml` is located.
-  Not supported by all the build backends yet.
 - ``urls`` lets you list any number of extra links to show on PyPI.
   Generally this could be to the source, documentation, issue trackers, etc.