Blubaugh, David A. wrote: > Is there a logical reason why Python 3 is not backwards compatible? > Yes. For a long time now the next *major* release of Python has been flagged as one which will take the opportunity to remove several design flaws from the original language and add features and syntax that couldn't be added as long as backwards compatibility was maintained.
There are, however, significant features in the 2.6 CPython implementation that will assist in migration, including an (optional) warning mode for usages that would cause problems in 3.0 and a tool that will migrate code that doesn't get flagged with warnings through to Python 3.0. So, in summary: 2.6 is the bridge to Python 3.0, and if you use it you won't have too much trouble migrating when the time comes. Note that Python 3.0 is currently at alpha2, and that even when it is released the "preferred" version will be 2.6. The early adopters will beat the snot out of 3.0, and us ordinary folk will probably not be ready to move until 3.1 or thereabouts. regards Steve -- Steve Holden +1 571 484 6266 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/ -- http://mail.python.org/mailman/listinfo/python-list