Update this PEP to current, harsh, reality. It's been rejected :) If at all
possible, the reasoning should be extended to include the real reasons it was rejected -- this is just guesswork from my side. (This means you, Guido, or anyone who can channel Guido enough to call himself Guido.)
This commit is contained in:
parent
616d974db7
commit
2ec18ca954
18
pep-0204.txt
18
pep-0204.txt
|
@ -2,7 +2,7 @@ PEP: 204
|
|||
Title: Range Literals
|
||||
Version: $Revision$
|
||||
Author: thomas@xs4all.net (Thomas Wouters)
|
||||
Status: Draft
|
||||
Status: Rejected
|
||||
Type: Standards Track
|
||||
Python-Version: 2.0
|
||||
Created: 14-Jul-2000
|
||||
|
@ -262,7 +262,21 @@ Open issues
|
|||
- The PyList_FromRange() and PyList_GetLenOfRange() functions need
|
||||
to be classified: are they part of the API, or should they be
|
||||
made private functions?
|
||||
|
||||
|
||||
|
||||
Rejection
|
||||
|
||||
After careful consideration, and a period of meditation, this
|
||||
proposal has been rejected. The open issues, as well as some
|
||||
confusion between ranges and slice syntax, raised enough questions
|
||||
for Guido not to accept it for Python 2.0, and later to reject the
|
||||
proposal altogether. The new syntax and its intentions were deemed
|
||||
not obvious enough.
|
||||
|
||||
[ TBD: Guido, ammend/confirm this, please. Preferably both; this
|
||||
is a PEP, it should contain *all* the reasons for rejection
|
||||
and/or reconsideration, for future reference. ]
|
||||
|
||||
|
||||
References:
|
||||
|
||||
|
|
Loading…
Reference in New Issue