bin/python3 symlink for python3X ports

[Ruslan Mahmatkhanov]

Dmitry Sivachenko wrote on 26.09.2012 13:14:
> On 26.09.2012 13:07, Ruslan Mahmatkhanov wrote:
>> Chris Rees wrote on 26.09.2012 13:03:
>>> On 26 Sep 2012 08:13, "Dmitry Sivachenko" <demon at freebsd.org> wrote:
>>>>
>>>> Hello!
>>>>
>>>> It is common to have both python-2 and python-3 packages installed.
>>>> To help transition it is convenient to have bin/python to point to
>>> python-2 binary.
>>>>
>>>> Now for every X in python3X we have a bin/python3.X binary.
>>>>
>>>> So for every new python3.X release one should change shebang line in
>>> scripts.
>>>>
>>>> I propose to tweak python3X ports so they create bin/python3 symlink
>>> pointing to the installed python3.X binary so that people can always use
>>> 'python3' name.
>>>>
>>>> What do you think?
>>>
>>> I think it's a great idea, at least minimising weird breakage when
>>> python
>>> is updated.
>>>
>>> Have you a patch?  Also, what do other OSes do?
>>>
>
>
> I don't have a patch but I can make one if you like.

Please do.

> I don't use other OSes so I have no idea what do they do with that
> problem and I don't see any reason why should we bother...

To no reinvent the wheel, for example. And because many software 
installers (setup.py, f.e.) are somewhat linux-centric: they looking for 
python2 or python3 binary (that we change to ${PYTHON_CMD} in our 
Makefile's).

-- 
Regards,
Ruslan

Tinderboxing kills... the drives.