mirror of
https://github.com/python/cpython.git
synced 2025-10-02 13:22:19 +00:00
[3.7] bpo-33518: Add PEP entry to documentation glossary (GH-6860) (#6934)
(cherry picked from commit d5f1442608
)
Co-authored-by: Andrés Delfino <adelfino@gmail.com>
This commit is contained in:
parent
09ca5906b7
commit
a3a554a536
1 changed files with 15 additions and 0 deletions
|
@ -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`.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue