Commit d5f14426 authored by Andrés Delfino's avatar Andrés Delfino Committed by Victor Stinner

bpo-33518: Add PEP entry to documentation glossary (GH-6860)

parent c2f082e9
...@@ -861,6 +861,21 @@ Glossary ...@@ -861,6 +861,21 @@ Glossary
:class:`str` or :class:`bytes` result instead, respectively. Introduced :class:`str` or :class:`bytes` result instead, respectively. Introduced
by :pep:`519`. 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 portion
A set of files in a single directory (possibly stored in a zip file) 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`. that contribute to a namespace package, as defined in :pep:`420`.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment