/usr/bin/env: python: No such file or directory

[Fernando Pérez]

Michael Hudson wrote:

> Fernando Pérez <fperez528 at yahoo.com> writes:
> 
>> It is NOT practical to expect users to write their scripts using
>> #!/usr/bin/env python2, simply because that's a weird, redhat only
>> default that breaks everywhere else. And what of code they download?
>> Now they have to manually inspect every script they get from the web
>> to replace python->python2? That's plain moronic.
> 
> No, those scripts should use distutils, which will get it right when
> it installs them.
> 
> $ python2 setup.py install --prefix=$HOME
> 
> Everyone should use distutils.  All the time.
> 
> Cheers,
> M.
> 

Well, not if it's a single script not intended as a package. It often happens 
that you find something useful on the web which is a stand-alone script. The 
widely accepted convention is that #!/usr/bin/env python will 'do the right 
thing' but unfortunately redhat breaks that. That's my beef.

f.