From 8cbde8a43769641373a681af4b0d72944af43f95 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Andr=C3=A9s=20Delfino?= Date: Tue, 22 May 2018 10:37:24 -0300 Subject: [PATCH] [2.7] bpo-33518: Add PEP entry to documentation glossary (GH-6860). (#6936) MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit (cherry picked from commit d5f144260886959c1fe06bc4506a23fd10f92348) Co-authored-by: Andrés Delfino --- Doc/glossary.rst | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/Doc/glossary.rst b/Doc/glossary.rst index cbd1237f8e5f..feb40a88bbed 100644 --- a/Doc/glossary.rst +++ b/Doc/glossary.rst @@ -625,6 +625,21 @@ Glossary :ref:`the difference between arguments and parameters `, and the :ref:`function` section. + 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`. + positional argument See :term:`argument`. -- 2.47.3