Skip to content

Commit ceec060

Browse files
committed
PEP 1 & 12: More explictly describe Post-History link format
1 parent e4c39c3 commit ceec060

File tree

2 files changed

+6
-2
lines changed

2 files changed

+6
-2
lines changed

pep-0001.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -660,7 +660,7 @@ The Created header records the date that the PEP was assigned a
660660
number, while Post-History is used to record the dates of and corresponding
661661
URLs to the Discussions-To threads for the PEP, with the former as the
662662
linked text, and the latter as the link target.
663-
Both headers should be in dd-mmm-yyyy format, e.g. 14-Aug-2001.
663+
Both sets of dates should be in ``dd-mmm-yyyy`` format, e.g. ``14-Aug-2001``.
664664

665665
Standards Track PEPs will typically have a Python-Version header which
666666
indicates the version of Python that the feature will be released with.

pep-0012.rst

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,11 @@ directions below.
121121
122122
- Leave Post-History alone for now; you'll add dates and corresponding links
123123
to this header each time you post your PEP to the designated discussion forum
124-
(and update the ``Discussions-To`` header with said link, as above).
124+
(and update the Discussions-To header with said link, as above).
125+
For each thread, use the date (in the ``dd-mmm-yyy`` format) as the
126+
linked text, and insert the URLs inline as anonymous reST `hyperlinks`_,
127+
with commas in between each posting.
128+
125129
If you posted threads for your PEP on August 14, 2001 and September 3, 2001,
126130
the Post-History header would look like, e.g.:
127131

0 commit comments

Comments
 (0)