"as" keyword woes
mccredie at gmail.com
Thu Dec 4 17:44:19 CET 2008
On Dec 4, 6:08 am, Steven D'Aprano <st... at REMOVE-THIS-
> 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.
Here is the list of downloads from python.org:
# Python 3.0 (December 3, 2008)
# Python 2.6 (October 1, 2008)
# Python 2.5.2 (February 22, 2008)
# Python 2.4.5 (March 11, 2008)
# Python 2.3.7 (March 11, 2008)
Notice that Python 2.3 was given the update treatment in March of this
year. I don't think I was being unreasonable. The point was that there
is that new releases don't _break_ anything. You should always expect
to have to test and update your code when going from Python2,x to
More information about the Python-list