On Wed, 03 Dec 2008 17:15:21 -0800, Matimus wrote: >> Couldn't we have continued along just fine using a smarter parser >> without elevating "as" to reserved status (and thus potentially >> breaking a 10+ years of existing code)? > > Nothing broke your code. It works just fine under the version it was > developed for. Who forced you to upgrade to python2.6?
Be reasonable. Python 2.5 is not very far away from being put into "security updates only" mode, and in a year or so it won't even get security updates. I dare say there are already platforms that use Python 2.6 as standard. Tying your software to an obsolete version of a language is a good way to force your software into obsolescence. Not that 2.5 is obsolete *now*. But it will be soon (for some definition of soon): in no more than a year or three, software that only runs on Python 2.5 would be like software that only runs on 2.3 now. -- Steven -- http://mail.python.org/mailman/listinfo/python-list
