RELEASED Python 2.6a1 and 3.0a3
Terry Reedy
tjreedy at udel.edu
Sun Mar 2 01:26:35 EST 2008
"Kay Schluehr" <kay.schluehr at gmx.net> wrote in message
news:eba3804e-4585-4ec7-85d2-a17513719025 at c33g2000hsd.googlegroups.com...
| On 1 Mrz., 19:51, Barry Warsaw <ba... at python.org> 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
| releases to Python 2.6 first just to migrate to Python 3.0?
You are quite free to update any code you want. Barry just said that 2.6
will help make the process easier. (At least it should for people who
prefer incremental changes to doing it all at once.) In any case, 2.5 and
earlier code that does not depend on bugs later fixed should usually run
unchanged in 2.6
| What are
| the inherent / technical reasons that prevent migration directly from
| 2.5 to 3.0?
None.
tjr
More information about the Python-list
mailing list