-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
PEP 1 & 12: Link Post-History dates to discussion threads (#2358)
- Loading branch information
1 parent
5c17c31
commit 7518444
Showing
3 changed files
with
32 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,7 +7,7 @@ Status: Active | |
Type: Process | ||
Content-Type: text/x-rst | ||
Created: 05-Aug-2002 | ||
Post-History: 30-Aug-2002 | ||
Post-History: `30-Aug-2002 <https://mail.python.org/archives/list/[email protected]/thread/KX3AS7QAY26QH3WIUAEOCCNXQ4V2TGGV/>`__ | ||
|
||
|
||
.. note:: | ||
|
@@ -113,20 +113,29 @@ directions below. | |
first appearance in. Do not use an alpha or beta release | ||
designation here. Thus, if the last version of Python was 2.2 alpha | ||
1 and you're hoping to get your new feature into Python 2.2, set the | ||
header to:: | ||
header to: | ||
|
||
.. code-block:: email | ||
Python-Version: 2.2 | ||
- Leave Post-History alone for now; you'll add dates to this header | ||
each time you post your PEP to the designated discussion forum (and announce | ||
it on Python-Dev, if needed; see the ``Discussions-To`` header above). | ||
- 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). | ||
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:: | ||
the Post-History header would look like, e.g.: | ||
|
||
Post-History: 14-Aug-2001, 03-Sept-2001 | ||
.. code-block:: email | ||
You must manually add new dates and commit them (with a pull request | ||
if you don't have push privileges). | ||
Post-History: `14-Aug-2001 <https://www.example.com/thread_1>`__, | ||
`03-Sept-2001 <https://www.example.com/thread_2>`__ | ||
You should add the new dates/links here as soon as you post a | ||
new discussion thread. | ||
|
||
- Add a Replaces header if your PEP obsoletes an earlier PEP. The | ||
value of this header is the number of the PEP that your new PEP is | ||
|
@@ -149,7 +158,9 @@ directions below. | |
For reference, here are all of the possible header fields (everything | ||
in brackets should either be replaced or have the field removed if | ||
it has a leading ``*`` marking it as optional and it does not apply to | ||
your PEP):: | ||
your PEP): | ||
|
||
.. code-block:: email | ||
PEP: [NNN] | ||
Title: [...] | ||
|
@@ -163,7 +174,7 @@ your PEP):: | |
Requires: *[NNN] | ||
Created: [DD-MMM-YYYY] | ||
Python-Version: *[M.N] | ||
Post-History: [DD-MMM-YYYY] | ||
Post-History: [`DD-MMM-YYYY <URL>`__] | ||
Replaces: *[NNN] | ||
Superseded-By: *[NNN] | ||
Resolution: | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters