Add note to all relevant PEPs pointing to their canonical PyPA specs

pep-0376.txt

@@ -10,6 +10,16 @@ Python-Version: 2.7, 3.2
 Post-History: `22-Jun-2009 <https://mail.python.org/archives/list/python-dev@python.org/thread/ILLTIOZAULMDY5CAS6GOITEYJ4HNFATQ/#ILLTIOZAULMDY5CAS6GOITEYJ4HNFATQ>`__
 
 
+.. important::
+   This PEP is a historical document; the up-to-date, canonical version
+   of the specification originally defined here is now
+   `maintained on the PyPA Specifications section of packaging.python.org
+   <https://packaging.python.org/en/latest/specifications/recording-installed-packages/>`__.
+   See the `PyPA specification update process
+   <https://www.pypa.io/en/latest/specifications/#handling-fixes-and-other-minor-updates>`__
+   for how to propose editorial and content changes.
+
+
 Abstract
 ========
 

pep-0427.txt

@@ -13,12 +13,16 @@ Created: 20-Sep-2012
 Post-History: 18-Oct-2012, 15-Feb-2013
 Resolution: https://mail.python.org/pipermail/python-dev/2013-February/124103.html
 
-Canonical specification
-=======================
 
-The canonical version of the wheel format specification is now maintained at
-https://packaging.python.org/specifications/binary-distribution-format/ .
-This may contain amendments relative to this PEP.
+.. important::
+   This PEP is a historical document; the up-to-date, canonical version
+   of the specification originally defined here is now
+   `maintained on the PyPA Specifications section of packaging.python.org
+   <https://packaging.python.org/en/latest/specifications/binary-distribution-format/>`__.
+   See the `PyPA specification update process
+   <https://www.pypa.io/en/latest/specifications/#handling-fixes-and-other-minor-updates>`_
+   for how to propose editorial and content changes.
+
 
 Abstract
 ========

pep-0566.rst

@@ -14,6 +14,16 @@ Replaces: 345
 Resolution: https://mail.python.org/pipermail/distutils-sig/2018-February/032014.html
 
 
+.. important::
+   This PEP is a historical change proposal; the up-to-date, canonical version
+   of the specification it modifies is
+   `maintained on the PyPA Specifications section of packaging.python.org
+   <https://packaging.python.org/en/latest/specifications/core-metadata/>`__.
+   See the `PyPA specification update process
+   <https://www.pypa.io/en/latest/specifications/#handling-fixes-and-other-minor-updates>`__
+   for how to propose editorial and content changes.
+
+
 Abstract
 ========
 

pep-0610.rst

@@ -12,6 +12,17 @@ Created: 21-Apr-2019
 Post-History:
 Resolution: https://discuss.python.org/t/1535/56
 
+
+.. important::
+   This PEP is a historical document; the up-to-date, canonical version
+   of the specification originally defined here is now
+   `maintained on the PyPA Specifications section of packaging.python.org
+   <https://packaging.python.org/en/latest/specifications/direct-url/>`__.
+   See the `PyPA specification update process
+   <https://www.pypa.io/en/latest/specifications/#handling-fixes-and-other-minor-updates>`_
+   for how to propose editorial and content changes.
+
+
 Abstract
 ========
 
@@ -26,15 +37,6 @@ additional metadata, to be added to the installed distribution by the
 installation front end, which records the Direct URL Origin for use by
 consumers which introspect the database of installed packages (see :pep:`376`).
 
-Provisional acceptance
-======================
-
-In accordance with the PyPA's specification process, this PEP has been
-`provisionally accepted <https://www.pypa.io/en/latest/specifications/#provisional-acceptance>`_
-for initial implementation in ``pip`` and other PyPA tools.
-
-During this time, the specification is still subject to revision based
-on real world experience with those initial implementations.
 
 Motivation
 ==========

pep-0621.rst

@@ -19,10 +19,15 @@ Post-History: 22-Jun-2020,
               31-Oct-2020
 Resolution: https://discuss.python.org/t/pep-621-round-3/5472/109
 
-.. note::
-   The official specification for the ``[project]`` table in
-   ``pyproject.toml`` now lives at
-   https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ .
+
+.. important::
+   This PEP is a historical document; the up-to-date, canonical version
+   of the specification originally defined here is now
+   `hosted on the PyPA Specifications section of packaging.python.org
+   <https://packaging.python.org/en/latest/specifications/declaring-project-metadata/>`__.
+   See the `PyPA specification update process
+   <https://www.pypa.io/en/latest/specifications/#handling-fixes-and-other-minor-updates>`__
+   for how to propose editorial and content changes.
 
 
 Abstract

pep-0627.rst

@@ -11,6 +11,16 @@ Created: 15-Jul-2020
 Resolution: https://discuss.python.org/t/pep-627/4126/42
 
 
+.. important::
+   This PEP is a historical change proposal; the up-to-date, canonical version
+   of the specification it modifies is
+   `maintained on the PyPA Specifications section of packaging.python.org
+   <https://packaging.python.org/en/latest/specifications/recording-installed-packages/>`__.
+   See the `PyPA specification update process
+   <https://www.pypa.io/en/latest/specifications/#handling-fixes-and-other-minor-updates>`__
+   for how to propose editorial and content changes.
+
+
 Abstract
 ========
 

pep-0643.rst

@@ -12,6 +12,16 @@ Post-History: 24-Oct-2020, 01-Nov-2020, 02-Nov-2020, 14-Nov-2020
 Resolution: https://discuss.python.org/t/pep-643-metadata-for-package-source-distributions/5577/53
 
 
+.. important::
+   This PEP is a historical change proposal; the up-to-date, canonical version
+   of the specification it modifies is
+   `maintained on the PyPA Specifications section of packaging.python.org
+   <https://packaging.python.org/en/latest/specifications/core-metadata/>`__.
+   See the `PyPA specification update process
+   <https://www.pypa.io/en/latest/specifications/#handling-fixes-and-other-minor-updates>`__
+   for how to propose editorial and content changes.
+
+
 Abstract
 ========
 
@@ -96,7 +106,7 @@ rules apply:
 2. If a field is marked as ``Dynamic``, it may contain any valid value in
    a wheel built from the sdist (including not being present at all).
 3. Backends MUST NOT mark a field as ``Dynamic`` if they can determine that
-   it was generated from data that will not change at build time. 
+   it was generated from data that will not change at build time.
 
 Backends MAY record the value they calculated for a field they mark as
 ``Dynamic`` in a source distribution. Consumers, however, MUST NOT treat