But that breaks other programs which actually need python to point to python3. I am looking for something like virtualenv. The method mentioned in the wiki(sourcing the virtualenv directory) wont work as it is not just the terminal session that needs to point to python2. I have looked at the source code and it is hardcoded to call bin/python when it executes a python script. Is it possible to change it to call bin/python2.7 as that is going to remain the same in all distros.
If this doesn't work, i was going to setup a dev environment on windows. Are there any problems with setting up the dev environment in windows. Regards, Sacheendra On Wed, Nov 20, 2013 at 2:44 PM, Ian Duffy <i...@ianduffy.ie> wrote: > Hi Sacheendra, > > Does placing python2.7 in your path before python3.3 help in any way? > > This process is described at: > https://wiki.archlinux.org/index.php/python > > They create a symbolic link from /usr/bin/python2 to ~/bin/python and then > place ~/bin into their path. > > > On 20 November 2013 10:11, Sacheendra Talluri <sacheendr...@gmail.com > >wrote: > > > Hi, > > I am new to Cloudstack > > > > In arch linux bin/python points to python3.3, but cloudstack needs it to > > point to python2.7 > > How do I get around this. For python programs i use virtualenv, but > > obviously it wont work for this. > > > > Has anybody got it working on arch linux. > > > > Regards, Sacheendra > > >
