1 |
On Wed, 2020-06-17 at 10:18 +0200, Ulrich Mueller wrote: |
2 |
> > > > > > On Tue, 16 Jun 2020, Michał Górny wrote: |
3 |
> > '/usr/bin/env python' (with no extra options) is the portable shebang. |
4 |
> |
5 |
> I still think this is a gross hack. You want your script to use the |
6 |
> correct interpreter (which is in /usr/bin, or the path substituted for |
7 |
> it at install time), not some random binary which happens to be found |
8 |
> in the user's ${PATH}. |
9 |
> |
10 |
|
11 |
How do you presume what the correct interpreter is, and why do you |
12 |
presume that users put 'random binaries' in their PATH? What if |
13 |
the user needs to override 'correct interpreter'? Requiring people to |
14 |
overwrite executables in /usr/bin sounds like a 'gross hack'. |
15 |
|
16 |
-- |
17 |
Best regards, |
18 |
Michał Górny |