Skip to content

Commit 531ee4f

Browse files
committed
Remove obselete mention of plain-text PEPs from Readme
1 parent 4db8581 commit 531ee4f

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

README.rst

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ https://www.python.org/dev/peps/. To learn more about the purpose of
99
PEPs and how to go about writing one, please start reading at `PEP 1
1010
<https://www.python.org/dev/peps/pep-0001/>`_.
1111
Note that PEP 0, the index PEP, is
12-
now automatically generated, and not committed to the repo.
12+
automatically generated and not committed to the repo.
1313

1414

1515
Contributing to PEPs
@@ -21,14 +21,11 @@ See the `Contributing Guidelines <./CONTRIBUTING.rst>`_.
2121
reStructuredText for PEPs
2222
=========================
2323

24-
Original PEP source should be written in reStructuredText format,
24+
PEP source text should be written in reStructuredText format,
2525
which is a constrained version of plaintext, and is described in
2626
`PEP 12 <https://www.python.org/dev/peps/pep-0012/>`_.
27-
Older PEPs were often written in a more mildly restricted
28-
plaintext format, as described in `PEP 9
29-
<https://www.python.org/dev/peps/pep-0009/>`_.
3027
The ``pep2html.py`` processing and installation script knows
31-
how to produce the HTML for either PEP format.
28+
how to produce the HTML for the PEP format.
3229

3330
To render the PEPs, you'll first need to install the requirements,
3431
(preferably in a fresh virtual environment):

0 commit comments

Comments
 (0)