Merge branch 'main' into patch-1

Author: woodruffw

source/shared/build-backend-tabs.rst

@@ -38,5 +38,5 @@
     .. code-block:: toml
 
         [build-system]
-        requires = ["uv_build >= 0.11.7, <0.12.0"]
+        requires = ["uv_build >= 0.11.21, <0.12.0"]
         build-backend = "uv_build"

source/specifications/core-metadata.rst

@@ -574,14 +574,14 @@ The format of a requirement string contains from one to four parts:
 * An environment marker after a semicolon. This means that the
   requirement is only needed in the specified conditions.
 
-See :pep:`508` for full details of the allowed format.
-
 The project names should correspond to names as found
 on the `Python Package Index`_.
 
 Version specifiers must follow the rules described in
 :doc:`version-specifiers`.
 
+See :ref:`dependency-specifiers` for full details of the allowed format.
+
 Examples::
 
     Requires-Dist: pkginfo
@@ -1071,6 +1071,9 @@ History
 - October 2025: Clarified that ``License-Expression`` applies to the containing
   distribution file and not the project itself.
 
+- January 2026: Replaced outdated direct reference to :pep:`508` with a
+  reference to :ref:`dependency-specifiers`.
+
 ----
 
 .. [1] reStructuredText markup:

source/specifications/dependency-groups.rst

@@ -209,8 +209,8 @@ The output is therefore valid ``requirements.txt`` data.
         realized_group = []
         for item in raw_group:
             if isinstance(item, str):
-                # packaging.requirements.Requirement parsing ensures that this is a valid
-                # PEP 508 Dependency Specifier
+                # packaging.requirements.Requirement parsing ensures that this
+                # is a valid dependency specifier
                 # raises InvalidRequirement on failure
                 Requirement(item)
                 realized_group.append(item)

source/specifications/dependency-specifiers.rst

@@ -106,8 +106,7 @@ Within a value, readers must accept and ignore spaces (including multiple
 consecutive spaces) before or after the colon, between the object reference and
 the left square bracket, between the extra names and the square brackets and
 colons delimiting them, and after the right square bracket. The syntax for
-extras is formally specified as part of :pep:`508` (as ``extras``) and
-restrictions on values specified in :pep:`685`.
+extras is formally specified in :ref:`dependency-specifiers`.
 For tools writing the file, it is recommended only to insert a space between the
 object reference and the left square bracket.
 
@@ -166,6 +165,8 @@ History
 - October 2017: This specification was written to formalize the existing
   entry points feature of setuptools (discussion_).
 
+- January 2026: Replaced outdated direct references to :pep:`508` and
+  :pep:`685` with a reference to :ref:`dependency-specifiers`.
 
 
 .. _discussion: https://mail.python.org/pipermail/distutils-sig/2017-October/031585.html

source/specifications/entry-points.rst

@@ -447,34 +447,57 @@ be ambiguous in the face of ``[project.scripts]`` and
 
 
 .. _pyproject-toml-dependencies:
-.. _pyproject-toml-optional-dependencies:
 
-``dependencies``/``optional-dependencies``
-------------------------------------------
+``dependencies``
+----------------
 
-- TOML_ type: Array of :pep:`508` strings (``dependencies``), and a
-  table with values of arrays of :pep:`508` strings
-  (``optional-dependencies``)
+- TOML_ type: Array of :ref:`dependency specifier <dependency-specifiers>`
+  strings (``dependencies``)
 - Corresponding :ref:`core metadata <core-metadata>` field:
-  :ref:`Requires-Dist <core-metadata-requires-dist>` and
-  :ref:`Provides-Extra <core-metadata-provides-extra>`
+  :ref:`Requires-Dist <core-metadata-requires-dist>`
 
-The (optional) dependencies of the project.
+``dependencies`` lists the expected dependencies of the project as an
+array of strings.
 
-For ``dependencies``, it is a key whose value is an array of strings.
 Each string represents a dependency of the project and MUST be
-formatted as a valid :pep:`508` string. Each string maps directly to
-a :ref:`Requires-Dist <core-metadata-requires-dist>` entry.
+formatted as a valid :ref:`dependency specifier <dependency-specifiers>`.
+
+Each string maps directly to a
+:ref:`Requires-Dist <core-metadata-requires-dist>` entry.
+
+Dependencies listed in this array are always considered
+for installation, but may still contain environment markers that cause them
+to be skipped in some environments.
+
+
+.. _pyproject-toml-optional-dependencies:
+
+``optional-dependencies``
+-------------------------
+
+- TOML_ type: table with string keys mapping to arrays of
+  :ref:`dependency specifier <dependency-specifiers>` strings (``optional-dependencies``)
+- Corresponding :ref:`core metadata <core-metadata>` fields:
+  :ref:`Requires-Dist <core-metadata-requires-dist>` and
+  :ref:`Provides-Extra <core-metadata-provides-extra>`
+
+``optional-dependencies`` is a table where each key specifies
+an extra and whose value is an array of strings using the same format as the
+``dependencies`` array (the strings in the
+arrays must be valid :ref:`dependency specifiers <dependency-specifiers>`).
 
-For ``optional-dependencies``, it is a table where each key specifies
-an extra and whose value is an array of strings. The strings of the
-arrays must be valid :pep:`508` strings. The keys MUST be valid values
+The keys MUST be valid values
 for :ref:`Provides-Extra <core-metadata-provides-extra>`. Each value
 in the array thus becomes a corresponding
 :ref:`Requires-Dist <core-metadata-requires-dist>` entry for the
 matching :ref:`Provides-Extra <core-metadata-provides-extra>`
 metadata.
 
+The optionality of these dependencies is recorded by modifying the environment
+marker clause on the related ``Requires-Dist`` entries to check the extra name.
+Optional dependencies are thus only considered for installation if installation
+if the associated extra name is requested.
+
 
 .. _pyproject-toml-import-names:
 
@@ -647,4 +670,7 @@ History
 - October 2025: The ``import-names`` and ``import-namespaces`` keys were added
   through :pep:`794`.
 
+- January 2026: Replaced outdated direct reference to :pep:`508` with a
+  reference to :ref:`dependency-specifiers`.
+
 .. _TOML: https://toml.io

source/specifications/pyproject-toml.rst

@@ -74,7 +74,7 @@ at their respective paths relative to the root directory of the sdist
 No other content of a sdist is required or defined. Build systems can store
 whatever information they need in the sdist to build the project.
 
-The tarball should use the modern POSIX.1-2001 pax tar format, which specifies
+The tarball must use the modern POSIX.1-2001 pax tar format, which specifies
 UTF-8 based file names. In particular, source distribution files must be readable
 using the standard library tarfile module with the open flag 'r:gz'.