In article <[EMAIL PROTECTED]>, Aahz <[EMAIL PROTECTED]> wrote: >In article <[EMAIL PROTECTED]>, >Anthony Irwin <[EMAIL PROTECTED]> wrote: >> >>#5 someone said that they used to use python but stopped because the >>language changed or made stuff depreciated (I can fully remember >>which) and old code stopped working. Is code written today likely to >>still work in 5+ years or do they depreciate stuff and you have to update? > >You're probably thinking of >http://www.gbch.net/gjb/blog/software/discuss/python-sucks.html > >Thing is, while he has a point, I don't think it's a very good one. For >example, just yesterday in upgrading from Java 1.4.2 to Java 5.0, I had >to fix a bunch of instances of "package foo.bar.baz;" to "package baz;" >because apparently the latter is now "correct". Bugfixes happen, and >sometimes they break working code.
Update: I was wrong about the package thing -- turned out that someone had made a backup copy of our code inside the source tree, and so ant merrily went along and gave nice "duplicate class" errors... -- Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ "Look, it's your affair if you want to play with five people, but don't go calling it doubles." --John Cleese anticipates Usenet -- http://mail.python.org/mailman/listinfo/python-list
