On Fri, Dec 23, 2016 at 12:26:54PM +1100, Sean Crosby wrote:
that's one of the things that symlinks are for.
e.g. I have python2.6, 2.7, 3.1, 3.2, 3.4, and 3.5 all installed in /usr/bin, with symlinks python & python2 pointing to 2.7, and python3 pointing to 3.5
All well and good if you're root....
and if you're not root, you can do the same things in ~/bin or edit the #! line of your script to point to your preferred interpreter. if it's not your script and you can't edit it, then either accept that it's going to be run with a system interpreter or write a wrapper script in ~/bin to call it with your preferred interpreter.
Yes but with the software our students use, they repackage python into a self contained directory, under the version of the software
they should edit the #! line then. it's not hard, and it avoids making an unmaintainable mess.
Hence why /usr/bin/env python is great.
it's not great. it's a mistake arising from inadequate understanding or knowledge of existing tools and practices. craig -- craig sanders <cas@taz.net.au>