In article <mailman.1660.1260434572.2873.python-l...@python.org>, Ned Deily <n...@acm.org> wrote: >In article <4b20ac0a$0$1596$742ec...@news.sonic.net>, > John Nagle <na...@animats.com> wrote: >> >> I'd argue against using Python 2.6 for production work. Either use >> Python 2.5, which is stable, or 3.x, which is bleeding-edge. 2.6 >> has some of the features of Python 3.x, but not all of them, and is >> neither fish nor fowl as a result. 2.6 is really more of a sideline >> that was used for trying out new features, not something suitable for >> production. > >I disagree with that advice, strongly. 2.6 not only has new features >but it has many bug fixes that have not and will not be applied to 2.5. >It is hardly a sideline.
Ditto -- we had some webserver crashes that were fixed by upgrading from 2.4 to 2.6 (we were already using 2.6 in the client and decided that skipping 2.5 on the server was best). -- Aahz (a...@pythoncraft.com) <*> http://www.pythoncraft.com/ Looking back over the years, after I learned Python I realized that I never really had enjoyed programming before. -- http://mail.python.org/mailman/listinfo/python-list
