Python 3.0 (Was: when will python 2.5 take in mainstream?)

Jean-Paul Calderone exarkun at divmod.com
Mon Feb 5 09:23:16 EST 2007


On Mon, 05 Feb 2007 07:01:26 -0700, Steven Bethard <steven.bethard at gmail.com> wrote:
>Laurent Pointal wrote:
>> For Python 3.0, AFAIK its a big rewrite and developers know that it will
>> be uncompatible in large parts with existing code.
>
>Wrong on both counts. ;-) Python 3.0 is not a rewrite. It's based on the
>same code base as the 2.X line, but with a lot of the old deprecated
>things removed. And, while Python 3.0 is allowing itself to break
>backwards compatibility, at least that the Python level, it should be
>largely compatible with the 2.X line. There will be some breakages, but
>(1) they shouldn't be too extensive and (2) there will be utilities to
>help you update your code. In many cases, it will be possible to write
>code that works in both Python 2.X and 3.0.

Hopefully that will be the case.  Misunderstandings aren't too surprising
though.  Until recently, it didn't appear that this would be the case at
all.  Of course, your statement isn't entirely accurate either.  For example,
many things which _aren't_ deprecated are being removed as well.  Some of
them may be deprecated in 2.x releases which haven't happened yet, but that
remains to be seen.  And 3.0 won't be "largely compatible" with any _existing_
2.x release, but hopefully a future 2.x release will add a usable transition
path.

Jean-Paul



More information about the Python-list mailing list