Skip to content

Commit

Permalink
Remove obselete mention of plain-text PEPs from Readme
Browse files Browse the repository at this point in the history
  • Loading branch information
CAM-Gerlach committed Feb 22, 2022
1 parent 4db8581 commit 531ee4f
Showing 1 changed file with 3 additions and 6 deletions.
9 changes: 3 additions & 6 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ https://www.python.org/dev/peps/. To learn more about the purpose of
PEPs and how to go about writing one, please start reading at `PEP 1
<https://www.python.org/dev/peps/pep-0001/>`_.
Note that PEP 0, the index PEP, is
now automatically generated, and not committed to the repo.
automatically generated and not committed to the repo.


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

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

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

0 comments on commit 531ee4f

Please sign in to comment.