forked from python/peps
-
Notifications
You must be signed in to change notification settings - Fork 0
Semi-official read-only mirror of the peps Mercurial repository
HelioCampos/peps
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
< 10000 td class="react-directory-row-commit-cell"> | ||||
Repository files navigation
Python Enhancement Proposals ============================ The PEPs in this repo are published automatically on the web at http://www.python.org/dev/peps/. To learn more about the purpose of PEPs and how to go about writing a PEP, please start reading at PEP 1 (pep-0001.txt in this repo). Note that PEP 0, the index PEP, is now automatically generated, and not committed to the repo. reStructuredText for PEPs ========================= Original PEP source may be written using two standard formats, a mildly idiomatic plaintext format and the reStructuredText format (also, technically plaintext). These two formats are described in PEP 9 and PEP 12 respectively. The pep2html.py processing and installation script knows how to produce the HTML for either PEP format. For processing reStructuredText format PEPs, you need the docutils package, which is available from PyPI (http://pypi.python.org). If you have pip, "pip install docutils" should install it. Generating HTML =============== Do not commit changes with bad formatting. To che 341A ck the formatting of a PEP, use the Makefile. In particular, to generate HTML for PEP 999, your source code should be in pep-0999.txt and the HTML will be generated to pep-0999.html by the command "make pep-0999.html". The default Make target generates HTML for all PEPs. If you don't have Make, use the pep2html.py script.
About
Semi-official read-only mirror of the peps Mercurial repository
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published
Languages
- Python 91.4%
- CSS 5.0%
- C 3.1%
- Makefile 0.5%