I was going to comment about this one "check it in, we'll add to it later", but then I realized it's not 100% clear whether this is a feature PEP or a meta-PEP? It focuses on features so by that yardstick it's a feature PEP. But in its list-of-miscellany nature it approximates a meta-PEP. Hmm, perhaps it ought to be PEP 3999 (which can be seen as minus one in the numbering scheme for Python-3000 PEPs :-)?
In any case let's not let it longer for long. Realistically, I think it can be a meta-PEP. --Guido On 4/2/06, Georg Brandl <[EMAIL PROTECTED]> wrote: > Guido van Rossum wrote: > > On 4/2/06, Georg Brandl <[EMAIL PROTECTED]> wrote: > >> A quick idea of mine: Wouldn't it be useful to maintain a list of what will > >> not change, collected in the discussions here? That way, people eager to > >> suggest > >> braces and whatnot can be referred to it. > >> > >> (I'd be volunteering to maintain such a list/PEP/whatever). > > > > Excellent idea! It should be one of the meta-peps (in the 3001-3099 range). > > > > Ideally the list should either point to the discusussion explaining > > the decision, or provide a capsule explanation. (Braces are exempted > > from this policy; if someone doesn't understand why we're not doing > > braces they should probably look elsewhere... :-) > > Here's a draft (please provide me with whatever you can remember, I've been > following the list on gmane and my history's therefore lost): > > PEP: XXX > Title: Things that will Not Change in Python 3000 > Version: $Revision$ > Last-Modified: $Date$ > Author: Georg Brandl <[EMAIL PROTECTED]> > Status: Draft > Type: Informational > Content-Type: text/x-rst > Created: 02-Apr-2006 > > > Abstract > ======== > > This PEP tries to list all BDFL pronouncements on Python 3000 that > refer to changes that will not happen and new features that will not > be introduced, sorted by topics, along with a short explanation or a > reference to the relevant thread on the python-3000 mailing list. > > > Core language > ============= > > * Python will not have programmable syntax. > > Thread: "It's a statement! It's a function! It's BOTH!" > http://mail.python.org/pipermail/python-3000/2006-April/000286.html > > * There won't be a syntax for ``zip()``-style parallel iteration. > > Thread: "Parallel iteration syntax", > http://mail.python.org/pipermail/python-3000/2006-March/000210.html > > > Standard types > ============== > > * Iterating over a dictionary will yield the keys. > > Thread: "Iterating over a dict", > http://mail.python.org/pipermail/python-3000/2006-April/000283.html > > > Coding style > ============ > > * The maximum line width will be 80 characters. > > Thread: "C style guide", > http://mail.python.org/pipermail/python-3000/2006-March/000131.html > > > Copyright > ========= > > This document has been placed in the public domain. > > _______________________________________________ > Python-3000 mailing list > Python-3000@python.org > http://mail.python.org/mailman/listinfo/python-3000 > Unsubscribe: > http://mail.python.org/mailman/options/python-3000/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
