When they have to ... One of the big things about Python is that its penetration slows it down. There's more legacy code and interdependant systems around now that Python is more successful and more mature.
Here's a thought -- perhaps it would be worth having some good ways to interact with Python from Python. Suppose you have some 2.4 code someplace, interacting with your mysqldb or whatever, and you don't want to rewrite it. So long as you have some kind of object broker, you could (plausibly) leave your 2.4 apps running with the old interpreter, but wrap them for Python 2.5 and use that in your new development. Ditto 3.0. Rather than having to re-write every interacting component, maybe it could be straightforward to all Python2.4 from Python2.5 to execute particular library calls. I'm not an expert, I don't know how you'd build such a system, but I do know that re-writing stuff is a real pain. Perhaps APIs for 2.5 and 3.0 could have a special version flag, and if not present or not compatible, a 2.4 interpreter could be called instead... Cheers, -T On Feb 5, 8:01 am, Dennis Lee Bieber <[EMAIL PROTECTED]> wrote: > On Sun, 4 Feb 2007 19:10:13 +0800, "Eric CHAO" <[EMAIL PROTECTED]> > declaimed the following in comp.lang.python: > > > When will all these applications support 2.5? > > cynical answer: when you download the sources and build them against > the 2.5 headers > > In the case of MySQLdb, one problem is that, as I recall, the > primary author does not have a Windows compatible build environment and > essentially relies upon others doing the Linux port to Windows and > releasing pre-built installers. > -- > Wulfraed Dennis Lee Bieber KD6MOG > [EMAIL PROTECTED] [EMAIL PROTECTED] > HTTP://wlfraed.home.netcom.com/ > (Bestiaria Support Staff: [EMAIL PROTECTED]) > HTTP://www.bestiaria.com/ -- http://mail.python.org/mailman/listinfo/python-list
