script has the same shebang in all cases. it depends on the path to the script which interpreter is used
no special environment setup, not additional wrappers, without changing shebang in scripts
just one configuration file/directory to specify which tool should use which environment. compatible with SCL, virtualenv and other available ways to get different version in one system
#!./python
to simulate the same tool in different path, i use symlink a or b to the original script.sh
case 1:
$ ./a
running in 2.5
case 2:
$ ./b
running in 2.6