Re: [Python-3000] pre-PEP: Things that Will Not Change in Python 3.0

2006-04-05 Thread Georg Brandl
Guido van Rossum wrote: > On 4/4/06, Georg Brandl <[EMAIL PROTECTED]> wrote: >> Guido van Rossum wrote: >> > 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 featu

Re: [Python-3000] pre-PEP: Things that Will Not Change in Python 3.0

2006-04-04 Thread Edward C. Jones
Greg Ewing <[EMAIL PROTECTED]> wrote > Subject: Re: [Python-3000] pre-PEP: Things that Will Not Change in > Python 3.0 > To: python-3000@python.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Guido

Re: [Python-3000] pre-PEP: Things that Will Not Change in Python 3.0

2006-04-04 Thread Greg Ewing
Guido van Rossum wrote: > Good idea. Maybe 3000 should then be the meta-meta PEP with the > Process for deciding Python 3000 Processes. And if we get too many more meta-meta-PEPs we'll need a meta-meta-meta-PEP on Procedure for Numbering Meta-Meta-PEPs. Not sure what number it should have, though

Re: [Python-3000] pre-PEP: Things that Will Not Change in Python 3.0

2006-04-04 Thread Guido van Rossum
On 4/4/06, Georg Brandl <[EMAIL PROTECTED]> wrote: > Guido van Rossum wrote: > > 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 > > i

Re: [Python-3000] pre-PEP: Things that Will Not Change in Python 3.0

2006-04-04 Thread Georg Brandl
Guido van Rossum wrote: > 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 >

Re: [Python-3000] pre-PEP: Things that Will Not Change in Python 3.0

2006-04-03 Thread Terry Reedy
"Guido van Rossum" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] >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? > In any case let's not let it longer for long. Real

Re: [Python-3000] pre-PEP: Things that Will Not Change in Python 3.0

2006-04-03 Thread Guido van Rossum
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, perh

Re: [Python-3000] pre-PEP: Things that Will Not Change in Python 3.0

2006-04-02 Thread Greg Ewing
Georg Brandl wrote: > PEP: XXX > Title: Things that will Not Change in Python 3000 > > ... > > Copyright > = I was expecting to see something like "The Python licence will not change" under this heading. :-) -- Greg ___ Python-3000 mailing li

[Python-3000] pre-PEP: Things that Will Not Change in Python 3.0

2006-04-02 Thread Georg Brandl
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