Remove most references to PEP numbers (#1091)

pypa · Dec 6, 2023 · 80f39ea · 80f39ea
1 parent 8926bac
commit 80f39ea
Show file tree

Hide file tree

Showing 4 changed files with 7 additions and 7 deletions.
diff --git a/docs/.snippets/links.txt b/docs/.snippets/links.txt
@@ -1,8 +1,6 @@
 [PEP 440 version specifiers]: https://peps.python.org/pep-0440/#version-specifiers
 [PEP 508]: https://peps.python.org/pep-0508/
 [PEP 517]: https://peps.python.org/pep-0517/
-[PEP 621]: https://peps.python.org/pep-0621/
-[PEP 631]: https://peps.python.org/pep-0631/
 [PEP 639]: https://peps.python.org/pep-0639/
 [PEP 660]: https://peps.python.org/pep-0660/
-[PEP 665]: https://peps.python.org/pep-0665/
+[project metadata standard]: https://packaging.python.org/en/latest/specifications/pyproject-toml/#declaring-project-metadata-the-project-table
diff --git a/docs/config/build.md b/docs/config/build.md
@@ -23,7 +23,7 @@ build-backend = "hatchling.build"
 
 The version of `hatchling` defined here will be used to build all targets.
 
-Hatchling is a [PEP 517][]/[PEP 660][] compatible build backend and is a dependency of Hatch itself.
+Hatchling is a standards-compliant[^1] build backend and is a dependency of Hatch itself.
 
 ## File selection
 
@@ -346,3 +346,5 @@ enable-by-default = false
 | `HATCH_BUILD_HOOKS_ENABLE` | `false` | Whether or not to enable all build hooks |
 | `HATCH_BUILD_HOOK_ENABLE_<HOOK_NAME>` | `false` | Whether or not to enable the build hook named `<HOOK_NAME>` |
 | `HATCH_BUILD_LOCATION` | `dist` | The location with which to build the targets; only used by the [`build`](../cli/reference.md#hatch-build) command |
+
+[^1]: Support for [PEP 517][] and [PEP 660][] guarantees interoperability with other build tools.
diff --git a/docs/config/metadata.md b/docs/config/metadata.md
@@ -3,7 +3,7 @@
 -----
 
 Project metadata is stored in a `pyproject.toml` file located at the root of a project's tree
-and is based entirely on [PEP 621][].
+and is based entirely on [the standard][project metadata standard].
 
 ## Name (*required*) ## {: #name }
 
@@ -183,7 +183,7 @@ Documentation = "..."
 
 ## Dependencies
 
-The format is based on [PEP 631][]. See the [dependency specification](dependency.md) section for more information.
+See the [dependency specification](dependency.md) page for more information.
 
 Entries support [context formatting](context.md) and [disallow direct references](#allowing-direct-references) by default.
 

diff --git a/docs/meta/faq.md b/docs/meta/faq.md
@@ -6,7 +6,7 @@
 
 ***Q***: What is the risk of lock-in?
 
-***A***: Not much! Other than the [plugin system](../plugins/about.md), everything uses Python's established standards by default. Project metadata is based entirely on [PEP 621][]/[PEP 631][], the build system is compatible with [PEP 517][]/[PEP 660][], versioning uses the scheme specified by [PEP 440](https://peps.python.org/pep-0440/#public-version-identifiers), dependencies are defined with [PEP 508][] strings, and environments use [virtualenv](https://github.com/pypa/virtualenv).
+***A***: Not much! Other than the [plugin system](../plugins/about.md), everything uses Python's established standards by default. Project metadata is based entirely on [the standard][project metadata standard], the build system is compatible with [PEP 517][]/[PEP 660][], versioning uses the scheme specified by [PEP 440](https://peps.python.org/pep-0440/#public-version-identifiers), dependencies are defined with [PEP 508][] strings, and environments use [virtualenv](https://github.com/pypa/virtualenv).
 
 ***Q***: Must one use all features?