"Dave Parker" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Kind of like how this year's program won't work on next year's > Python? Except Flaming Thunder is faster. ;)
To be fair (and accurate), Python 3.0 has been in development for a long time without being marketed for production use. Furthermore, there is no reason to think 3.0 will take over "next year." It's already been stated that it may be years before it does, and meanwhile 2.x will continue to be developed. Also, and this is purely my novice opinion, it seems like the incompatibilites are mainly going to come from program written in older versions of Python. The big, noticeable changes in 3.0 hardly seem to affect anything you'll write in recent versions of Python (and that 2to3 won't fix otherwise). -- http://mail.python.org/mailman/listinfo/python-list
