On Tuesday, April 14, 2015 08:10:49 AM Barry Warsaw wrote: > On Apr 14, 2015, at 12:38 AM, Scott Kitterman wrote: > >If you want python (which include /usr/bin/python), install it. If you > >want python3, then the interpreter you're looking for is found at > >/usr/bin/python3. > I just don't want it to fail mysteriously. > > When there's no Python 2 by default, command-not-found will solve the > type-it-at-the-shell failure mode just fine: > > $ python > The program 'python is currently not installed. You can install it by > typing: sudo apt-get install python-for-dinosaurs > > But it fails unhelpfully when you use it in a shebang. > > $ /tmp/foo.py > bash: /tmp/foo.py: /usr/bin/python: bad interpreter: No such file or > directory > > Let's make the latter more helpful. OK, but running an incompatible interpreter doesn't fall into that category. Scott K
Attachment:
signature.asc
Description: This is a digitally signed message part.