Re: Butchered python configuration ...

[itsovermyhead <itsovermyhead@googlemail.com>]

FYI - This problem was solved by a kind and clear post. See below.

http://lists.debian.org/debian-user/2009/04/msg02759.html

You lot on this list are grumpy buggers...




2009/4/29 Dmitrijs Ledkovs <dmitrij.ledkov@gmail.com>:
> 2009/4/28 itsovermyhead <itsovermyhead@googlemail.com>:
>> 2009/4/28 Piotr Ożarowski <piotr@debian.org>:
>>> [itsovermyhead, 2009-04-28]
>>>> dev3:/usr/bin# ls -la python*
>>>> -rwxr-xr-x 2 root root 1015264 2008-10-23 08:53 python
>>>> -rwxr-xr-x 2 root root 1015264 2008-10-23 08:53 python2.4
>>>> -rwxr-xr-x 1 root root    1276 2008-10-23 08:53 python2.4-config
>>>
>>> I'd start with:
>>> # rm /usr/bin/python # and all other local files
>>> # ln -s /usr/bin/python2.4 /usr/bin/python
>>
>> Thanks for your reply Piotr - are you confident about this solution? A
>> lot of people use this server so I want to be as sure as possible that
>> this is the right approach to the problem.
>>
>> Can you could explain your reasoning so I can understand what you're
>> proposing better.
>>
>> Cheers
>>
>> S
>>
>
> As far as i know. python binary is always the default python
> interpreter which points to one of the supported version and by
> default it points (symlink) to python2.5 in lenny (I think). the
> pythonX.Y are actually real binaries.
>
> If you are not convineced I gues you should
>
> $apt-get source python
>
> and study the packaging.
>
>
> --
> With best regards
>
>
> Dmitrijs Ledkovs (for short Dima),
> Ледков Дмитрий Юрьевич
>