On Sun, 03 Aug 2008 14:01:49 -0400, Allen <br***************@yahoo.comwrote:
I'm in the process of developing an application that will use Python for
a scripting support. In light of the upcoming changes to Python, I was
wondering if it is possible to link to and use two different versions of
Python so that in the future, scripts could be migrated to the new
version, and older scripts would still work as well. If so are there
any code examples of this.
I cannot answer that, sorry.
But if I were you, I'd pick a current, stable Python version for my
application, and stop worrying for now.
If there is a new, incompatible Python version (I assume you're
talking about Py3k?) these things will happen:
- people around the world will decide to migrate
- people will gain experience with migrating Python code
- Python 2.x will start to look obsolete
- things like Linux distributions and web hosting companies will
stop offering Python 2.x
- you will be forced (for practical reasons, or to avoid looking silly)
to migrate your application (and break old scripts)
All this will happen *slowly* -- I believe so slowly that you will
have plenty of time to act later. And your users (or whoever has to
deal with the scripts) will not be alone; lots of people will sit
around migrating old Python code.
(Caveat: I don't know much about the Py3k transition, just about other
cases like that. Killing off an old language dialect takes time!)
/Jorgen
--
// Jorgen Grahn <grahn@ Ph'nglui mglw'nafh Cthulhu
\X/ snipabacken.se R'lyeh wgah'nagl fhtagn!