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 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? What are
> the inherent / technical reasons that prevent migration directly from
> 2.5 to 3.0?
One of the stated goals of the migration is that the '2to3' program
will only migrate Python 2.6 code -> Python 3.0 code. So, the
smoothest migration path will be:
* get your program working with Python 2.6; then
* use '2to3' to automatically translate that program to work with
Python 3.0; then
* stop using Python 2.x for that program, only use Python 3.x.
Another reason is that good features from Python 3.0 will likely be
backported (if possible) to Python 2.6.x, but not to any earlier
version.
--
\ "Dad always thought laughter was the best medicine, which I |
`\ guess is why several of us died of tuberculosis." -- Jack |
_o__) Handey |
Ben Finney
--
http://mail.python.org/mailman/listinfo/python-list
