gpsd-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ✘python shebang, yet again


From: Gary E. Miller
Subject: Re: ✘python shebang, yet again
Date: Thu, 24 Sep 2020 18:09:09 -0700

Yo Greg!

On Thu, 24 Sep 2020 20:57:32 -0400
Greg Troxel <gdt@lexort.com> wrote:

> "Gary E. Miller" <gem@rellim.com> writes:
> 
> > I could live with removing /usr/bin/env IFF target_python is a full
> > path.  Otherwise keep the /usr/bin/env  
> 
> That is probably the best thing in terms of making the most people
> happy.  If people want to set target_python to not a full path, which
> I understand many do, then they do need env.  But for those who pass
> a full path, I think essentially all of them just want that executed.

Agreed.  I'll give this another day before I commit anything.

> (The point of using a full path is to bind to a particular python
> build at gpsd configure/build time, rather than having it end up
> using one at runtime that may or may not have been changed.  But I've
> said that before, and the PEP people don't value that property.)

Nor do I believe that is even possible.  A topic for another day.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        gem@rellim.com  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

Attachment: pgpg7cqGLl8xR.pgp
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]