Re: python / python3 3 pybuild and bin script
On Wed, Feb 05, 2014 at 04:16:06PM +0800, Thomas Goirand wrote:
> Hi,
Hello
>
> Thanks for raising this important topic.
>
> What I've been doing up to now, is renaming "foo" into "python3-foo" and
> "python2-foo", then I use update-alternatives to provide /usr/bin/foo,
> with the python2 version having the priority. Sometimes I've even used
> "foo-python3" and "foo-python2" (and I feel bad about my lack of
> consistency, though since we have no defined standards...).
> Though I'm seeing that you just add a "3" to the python3 version, which
> in some way works well too. Though do you also add a "2" for the python2
> version? Do you use update-alternatives?
No I do not have a 2 for the current script.
I think that I should have a spyder2.7 and a link to spyder ->
spyder2.7 like python2.6 python2.7 and python
I considere that spyder3 is not equivalent to spyder2 so I do not want
to use the alternatives for this purpose.
>
> Also, I've experienced that using update-alternatives the correct way is
> somehow counter-intuitive and badly documented (see: #71621).
I never try to use this system since I am not very confortable with it.
>
> Thoughts anyone? What would you consider best practice?
Yes opinions of other would be interesing.
See you
Fred
--
GPG public key 4096R/4696E015 2011-02-14
fingerprint = E92E 7E6E 9E9D A6B1 AA31 39DC 5632 906F 4696 E015
uid Picca Frédéric-Emmanuel <picca@synchrotron-soleil.fr>
GPG public key 1024D/A59B1171 2009-08-11
fingerprint = 1688 A3D6 F0BD E4DF 2E6B 06AA B6A9 BA6A A59B 1171
uid Picca Frédéric-Emmanuel <picca@debian.org>
Reply to: