Benjamin Kaplan wrote:
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.
Which Linux distribution are you using?
My Debian system does what I consider to be the Right Thing: python
scripts provided by Debian bin with "#!/usr/bin/python". This allows
me to install some version of Python in another directory and have
that one first in my $PATH, so that if I type python, I get the one
I want and if a system utility needs the system Python, they'll get
their version and nothing breaks.
I happen to be a fan of virtualenv; virtualenv depends on this feature.
Cheers,
-- HansM
--
http://mail.python.org/mailman/listinfo/python-list
