Re: [PATCH] Use env to find python

On Tue, Jun 16, 2020 at 1:55 PM Zac Medico <[email protected]> wrote:
>
> On 6/16/20 10:46 AM, Mike Gilbert wrote:
> > On Tue, Jun 16, 2020 at 1:45 PM Mike Gilbert <[email protected]> wrote:
> >>
> >> On Mon, Jun 15, 2020 at 9:39 AM Sid Spry <[email protected]> wrote:
> >>>
> >>> On Mon, Jun 15, 2020, at 2:36 AM, Ulrich Mueller wrote:
> >>>> But we know that it is in /usr/bin, so why add yet another indirection?
> >>>>
> >>>> Attachments:
> >>>> * signature.asc
> >>>
> >>> Ah, sorry -- I forgot to note this here. If you wish to support prefix it is possible it may not be in /usr/bin. Granted I am not sure if the prefix stage3 I was using is old enough to be broken in some way, but adding this would prevent future breakage.
> >>
> >> The portage ebuild and the python distutils module already take care
> >> of updating shebangs at install time.
> >
> > I suppose your patch might be useful if you are trying to run portage
> > from a git checkout on a prefix system.
> >
>
> So, given that the ebuild updates shebangs automatically, should't we
> optimize the default shebangs to be as flexible as possible?

Yes, that makes sense.

However, we should test to make sure that distutils is smart enough to
parse that "/usr/bin/env -S python" string and replace it with
version-specific python shebang.