[Python-checkins] [3.7] bpo-33518: Add PEP entry to documentation glossary (GH-6860) (#6934)
Victor Stinner
webhook-mailer at python.org
Fri May 18 19:44:25 EDT 2018
https://github.com/python/cpython/commit/a3a554a536599189166843cd80e62d02b2b68aa8
commit: a3a554a536599189166843cd80e62d02b2b68aa8
branch: 3.7
author: Andrés Delfino <adelfino at gmail.com>
committer: Victor Stinner <vstinner at redhat.com>
date: 2018-05-19T01:44:18+02:00
summary:
[3.7] bpo-33518: Add PEP entry to documentation glossary (GH-6860) (#6934)
(cherry picked from commit d5f144260886959c1fe06bc4506a23fd10f92348)
Co-authored-by: Andrés Delfino <adelfino at gmail.com>
files:
M Doc/glossary.rst
diff --git a/Doc/glossary.rst b/Doc/glossary.rst
index 2eab00314682..a90f176db7ba 100644
--- a/Doc/glossary.rst
+++ b/Doc/glossary.rst
@@ -837,6 +837,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`.
More information about the Python-checkins
mailing list