Skip to content

Commit

Permalink
PEP 1 & 12: More explictly describe Post-History link format
Browse files Browse the repository at this point in the history
  • Loading branch information
CAM-Gerlach committed Mar 8, 2022
1 parent e4c39c3 commit ceec060
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 2 deletions.
2 changes: 1 addition & 1 deletion pep-0001.txt
Original file line number Diff line number Diff line change
Expand Up @@ -660,7 +660,7 @@ The Created header records the date that the PEP was assigned a
number, while Post-History is used to record the dates of and corresponding
URLs to the Discussions-To threads for the PEP, with the former as the
linked text, and the latter as the link target.
Both headers should be in dd-mmm-yyyy format, e.g. 14-Aug-2001.
Both sets of dates should be in ``dd-mmm-yyyy`` format, e.g. ``14-Aug-2001``.

Standards Track PEPs will typically have a Python-Version header which
indicates the version of Python that the feature will be released with.
Expand Down
6 changes: 5 additions & 1 deletion pep-0012.rst
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,11 @@ directions below.
- Leave Post-History alone for now; you'll add dates and corresponding links
to this header each time you post your PEP to the designated discussion forum
(and update the ``Discussions-To`` header with said link, as above).
(and update the Discussions-To header with said link, as above).
For each thread, use the date (in the ``dd-mmm-yyy`` format) as the
linked text, and insert the URLs inline as anonymous reST `hyperlinks`_,
with commas in between each posting.

If you posted threads for your PEP on August 14, 2001 and September 3, 2001,
the Post-History header would look like, e.g.:

Expand Down

0 comments on commit ceec060

Please sign in to comment.