From 88a91146012db92a63a458b9e9654414224ff004 Mon Sep 17 00:00:00 2001 From: Guido van Rossum Date: Fri, 15 Sep 2000 20:50:35 +0000 Subject: [PATCH] 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.) --- pep-0042.txt | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/pep-0042.txt b/pep-0042.txt index 1400ec54c..74b8e4f31 100644 --- a/pep-0042.txt +++ b/pep-0042.txt @@ -1,5 +1,5 @@ PEP: 42 -Title: Small Feature Requests +Title: Feature Requests Version: $Revision$ Author: Jeremy Hylton Status: Active @@ -8,11 +8,23 @@ Created: 12-Sep-2000 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 - 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. + 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