| @@ -837,6 +837,21 @@ Glossary |
|
|
| 837 |
837 |
:class:`str` or :class:`bytes` result instead, respectively. Introduced |
| 838 |
838 |
by :pep:`519`. |
| 839 |
839 |
|
|
840 |
+ PEP |
|
841 |
+ Python Enhancement Proposal. A PEP is a design document |
|
842 |
+ providing information to the Python community, or describing a new |
|
843 |
+ feature for Python or its processes or environment. PEPs should |
|
844 |
+ provide a concise technical specification and a rationale for proposed |
|
845 |
+ features. |
|
846 |
+ |
|
847 |
+ PEPs are intended to be the primary mechanisms for proposing major new |
|
848 |
+ features, for collecting community input on an issue, and for documenting |
|
849 |
+ the design decisions that have gone into Python. The PEP author is |
|
850 |
+ responsible for building consensus within the community and documenting |
|
851 |
+ dissenting opinions. |
|
852 |
+ |
|
853 |
+ See :pep:`1`. |
|
854 |
+ |
| 840 |
855 |
portion |
| 841 |
856 |
A set of files in a single directory (possibly stored in a zip file) |
| 842 |
857 |
that contribute to a namespace package, as defined in :pep:`420`. |