On Mon, Jun 14, 2010 at 3:09 AM, Alexzive <zasaconsult...@gmail.com> wrote: > thanks guys, > > the solution for me was > > python2.4 setup.py install --prefix=/usr/local > > cheers, AZ >
Don't do that! Like Steven said, you'll kill your system that way. Lots of programs in Linux use Python and those programs expect /usr/bin/env python to map to python2.6. Other versions of Python should be referenced by the version: so python2.4 for Python 2.4, python3 or python3.1 if you decide to install Python 3.1. > On Jun 14, 11:00 am, Steven D'Aprano <st...@remove-this- > cybersource.com.au> wrote: >> On Mon, 14 Jun 2010 01:30:09 -0700, Alexzive wrote: >> > what to change in order to get "python" calling python 2.4.3 instead of >> > 2.6.4 (at least during python setup.py build)? >> >> That will do bad things to your system, which will be expecting the >> system Python to be 2.6 and instead will be 2.4. You will probably find >> system tools will start to fail. >> >> > I suppose I need something like changing the link to /usr/local/bin/ >> > python.. >> > but I fear to do something bad by myself.. please help! >> >> Yes, that will do it, but if you do, you will probably break things. Best >> to just call the python2.4 binary directly. >> >> If you call >> >> python2.4 >> >> from the command line, what happens? >> >> -- >> Steven > > -- > http://mail.python.org/mailman/listinfo/python-list > -- http://mail.python.org/mailman/listinfo/python-list
