This PEP is not just for small feature requests; it's also a temporary

placeholder for large feature requests, while their PEP hasn't been
written yet.  Changed the title and added some word to the intro to
this effect.

(Discussed by Tim & Guido.)
This commit is contained in:
Guido van Rossum 2000-09-15 20:50:35 +00:00
parent 6dc955c7c4
commit 88a9114601
1 changed files with 15 additions and 3 deletions

View File

@ -1,5 +1,5 @@
PEP: 42 PEP: 42
Title: Small Feature Requests Title: Feature Requests
Version: $Revision$ Version: $Revision$
Author: Jeremy Hylton <jeremy@beopen.com> Author: Jeremy Hylton <jeremy@beopen.com>
Status: Active Status: Active
@ -8,11 +8,23 @@ Created: 12-Sep-2000
Introduction Introduction
This PEP contains a list of small feature requests that may be This PEP contains a list of feature requests that may be
considered for future versions of Python. Large feature requests considered for future versions of Python. Large feature requests
are not included here, but are described in separate PEPs. See should not be included here, but should be described in separate
PEPs; however a large feature request that doesn't have its own
PEP can be listed here until its own PEP is created. See
pep-0000.txt for details. pep-0000.txt for details.
This PEP was created to allow us to close bug reports that are
really feature requests. Marked as Open, they distract from the
list of real bugs (which should ideally be less than a page).
Marked as Closed, they tend to be forgotten. The procedure now
is: if a bug report is really a feature request, add the feature
request to this PEP, and close the bug report with a comment
saying that this is the case (mentioning the PEP explicitly). It
is also acceptable to move large feature requests directly from
the bugs database to a separate PEP.
Core Language / Builtins Core Language / Builtins