Re: RELEASED Python 2.6a1 and 3.0a3

2008-03-03 Thread Terry Reedy
"Tim Roberts" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] | Kay Schluehr <[EMAIL PROTECTED]> wrote: | >"The master said so" isn't an entirely satisfying answer. | | Nevertheless, it IS the answer for many questions in the Python world. But not for the questions about 2to3 Curren

Re: RELEASED Python 2.6a1 and 3.0a3

2008-03-03 Thread dave_mikesell
On Mar 1, 10:53 pm, Kay Schluehr <[EMAIL PROTECTED]> wrote: > On 1 Mrz., 19:51, Barry Warsaw <[EMAIL PROTECTED]> wrote: > > > Python 2.6 is not only the next advancement in the Python 2 series, it > > is also a transitionary release, helping developers begin to prepare > > their code for Python 3.0

Re: RELEASED Python 2.6a1 and 3.0a3

2008-03-03 Thread dave_mikesell
On Mar 1, 10:53 pm, Kay Schluehr <[EMAIL PROTECTED]> wrote: > On 1 Mrz., 19:51, Barry Warsaw <[EMAIL PROTECTED]> wrote: > > > Python 2.6 is not only the next advancement in the Python 2 series, it > > is also a transitionary release, helping developers begin to prepare > > their code for Python 3.0

Re: RELEASED Python 2.6a1 and 3.0a3

2008-03-03 Thread Paul Boddie
On 2 Mar, 10:02, Kay Schluehr <[EMAIL PROTECTED]> wrote: > On 2 Mrz., 06:53, Ben Finney <[EMAIL PROTECTED]> > wrote: > > > One of the stated goals of the migration is that the '2to3' program > > will only migrate Python 2.6 code -> Python 3.0 code. > > Yes, I know. Why? > > "The master said so" isn

Re: RELEASED Python 2.6a1 and 3.0a3

2008-03-02 Thread Tim Roberts
Kay Schluehr <[EMAIL PROTECTED]> wrote: > >On 2 Mrz., 06:53, Ben Finney <[EMAIL PROTECTED]> >wrote: > >> One of the stated goals of the migration is that the '2to3' program >> will only migrate Python 2.6 code -> Python 3.0 code. > >Yes, I know. Why? > >"The master said so" isn't an entirely satisf

Re: RELEASED Python 2.6a1 and 3.0a3

2008-03-02 Thread Ben Finney
Kay Schluehr <[EMAIL PROTECTED]> writes: > On 2 Mrz., 06:53, Ben Finney <[EMAIL PROTECTED]> > wrote: > > > One of the stated goals of the migration is that the '2to3' > > program will only migrate Python 2.6 code -> Python 3.0 code. > > Yes, I know. Why? > > "The master said so" isn't an entire

Re: RELEASED Python 2.6a1 and 3.0a3

2008-03-02 Thread Carl Banks
On Mar 2, 4:02 am, Kay Schluehr <[EMAIL PROTECTED]> wrote: > On 2 Mrz., 06:53, Ben Finney <[EMAIL PROTECTED]> > wrote: > > > One of the stated goals of the migration is that the '2to3' program > > will only migrate Python 2.6 code -> Python 3.0 code. > > Yes, I know. Why? > > "The master said so" i

Re: RELEASED Python 2.6a1 and 3.0a3

2008-03-02 Thread Kay Schluehr
On 2 Mrz., 06:53, Ben Finney <[EMAIL PROTECTED]> wrote: > One of the stated goals of the migration is that the '2to3' program > will only migrate Python 2.6 code -> Python 3.0 code. Yes, I know. Why? "The master said so" isn't an entirely satisfying answer. What are the *technical reasons* that

Re: RELEASED Python 2.6a1 and 3.0a3

2008-03-01 Thread Terry Reedy
"Kay Schluehr" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] | On 1 Mrz., 19:51, Barry Warsaw <[EMAIL PROTECTED]> wrote: | | > Python 2.6 is not only the next advancement in the Python 2 series, it | > is also a transitionary release, helping developers begin to prepare | > their co

Re: RELEASED Python 2.6a1 and 3.0a3

2008-03-01 Thread Ben Finney
Kay Schluehr <[EMAIL PROTECTED]> writes: > On 1 Mrz., 19:51, Barry Warsaw <[EMAIL PROTECTED]> wrote: > > > Python 2.6 is not only the next advancement in the Python 2 series, it > > is also a transitionary release, helping developers begin to prepare > > their code for Python 3.0. > > Isn't this

Re: RELEASED Python 2.6a1 and 3.0a3

2008-03-01 Thread Kay Schluehr
On 1 Mrz., 19:51, Barry Warsaw <[EMAIL PROTECTED]> wrote: > Python 2.6 is not only the next advancement in the Python 2 series, it > is also a transitionary release, helping developers begin to prepare > their code for Python 3.0. Isn't this a silly idea? People have to migrate from 2.5 or lower