On Sun, 23 Oct 2016, Stuart Henderson wrote:
>> #!/usr/bin/env python
>
> Opinions vary but I'm not a fan of using env for this, I don't normally
> want to trust the first file of that name found in the path.
There are two kinds of people: those that know exactly what their $PATH
is, and those wh
On 2016-10-22, Ovidiu M wrote:
> Hi everyone,
>
> I wrote a script which may end up as part of a package on various
> Linux and BSD flavors, and I have hit the problem of getting the
> shebang working everywhere. You might know that Python is installed in
> different locations, with the binary hav
On 23 October 2016 at 03:01, john slee wrote:
> Meta: this "how do I manage multiple Pythons?" thing has come up a couple
> of times lately; are people interested in a FAQ section?
>
> On 23 October 2016 at 03:54, Eugene Yunak wrote:
>> I'd set the shebang to `/usr/bin/env python3`, or `/usr/bin/
Meta: this "how do I manage multiple Pythons?" thing has come up a couple
of times lately; are people interested in a FAQ section?
On 23 October 2016 at 03:54, Eugene Yunak wrote:
> I'd set the shebang to `/usr/bin/env python3`, or `/usr/bin/env python`
if you
> do not care whether 2 or 3 would b
On 22 October 2016 at 18:04, Ovidiu M wrote:
> Hi everyone,
>
> I wrote a script which may end up as part of a package on various
> Linux and BSD flavors, and I have hit the problem of getting the
> shebang working everywhere. You might know that Python is installed in
> different locations, with
Hi everyone,
I wrote a script which may end up as part of a package on various
Linux and BSD flavors, and I have hit the problem of getting the
shebang working everywhere. You might know that Python is installed in
different locations, with the binary having different names (for
example python som
6 matches
Mail list logo