Huh , didn't know that. Won't the code only work through one version though? They aren't backwards compatible.
Correct, the code may not work with just any version. But you can have all python versions installed on your system independent of one another, and you can launch your scripts with any version you would like.
Each independent installation of python has its own installation files. You just have to invoke the interpreter manually, depending on which version you want to use. For example, my python 3.0 Windows installation is located at C:\python30. So to launch my python script, I would just do:
C:\python30\python.exe my_script.py. If I want to use 27 install, C:\python27\python.exe my_script.py. So you can have all the latest python versions installed on your system, and if you happen to come across a script that is using an older python version, just use the older interpreter. The interpreter is just a program, python.exe. You "launch" your programs by passing the script as a command line argument to the interpreter.
In linux the first line of the script with the #! tells you the location of the interpreter that will be used to execute the script. You will often see this as the first line:
#! /usr/bin/env pythonThis gets the location of python from the $PATH.
You can explicitly specify the interpreter you want to use:
#! /usr/local/bin/python3.0
So there is no such thing as updating. You can have all versions installed simultaneously then launch your scripts with any version you would like. That is what the launchscript.bat and launchscript.sh do.
Edited by compex, 25 December 2011 - 11:45 PM.