summaryrefslogtreecommitdiffstats
path: root/Doc/glossary.rst
diff options
context:
space:
mode:
authorAndrés Delfino <adelfino@gmail.com>2018-05-17 07:51:50 (GMT)
committerVictor Stinner <vstinner@redhat.com>2018-05-17 07:51:50 (GMT)
commitd5f144260886959c1fe06bc4506a23fd10f92348 (patch)
tree868e75307bc950079d04c8a7a1d677ee86c7c97a /Doc/glossary.rst
parentc2f082e9d164acfa8f96de9526f0f47ae92c426a (diff)
downloadcpython-d5f144260886959c1fe06bc4506a23fd10f92348.zip
cpython-d5f144260886959c1fe06bc4506a23fd10f92348.tar.gz
cpython-d5f144260886959c1fe06bc4506a23fd10f92348.tar.bz2
bpo-33518: Add PEP entry to documentation glossary (GH-6860)
Diffstat (limited to 'Doc/glossary.rst')
-rw-r--r--Doc/glossary.rst15
1 files changed, 15 insertions, 0 deletions
diff --git a/Doc/glossary.rst b/Doc/glossary.rst
index 16b5267..13d0b9e 100644
--- a/Doc/glossary.rst
+++ b/Doc/glossary.rst
@@ -861,6 +861,21 @@ Glossary
:class:`str` or :class:`bytes` result instead, respectively. Introduced
by :pep:`519`.
+ PEP
+ Python Enhancement Proposal. A PEP is a design document
+ providing information to the Python community, or describing a new
+ feature for Python or its processes or environment. PEPs should
+ provide a concise technical specification and a rationale for proposed
+ features.
+
+ PEPs are intended to be the primary mechanisms for proposing major new
+ features, for collecting community input on an issue, and for documenting
+ the design decisions that have gone into Python. The PEP author is
+ responsible for building consensus within the community and documenting
+ dissenting opinions.
+
+ See :pep:`1`.
+
portion
A set of files in a single directory (possibly stored in a zip file)
that contribute to a namespace package, as defined in :pep:`420`.