On Fri, Oct 23, 2020 at 10:27:51AM -0500, DJ Lucas via blfs-dev wrote:
> On October 23, 2020 10:15:09 AM CDT, Ken Moffat via blfs-dev
> <[email protected]> wrote:
> >On Fri, Oct 23, 2020 at 09:04:53AM +0200, Pierre Labastie via blfs-dev
> >wrote:
> >> > Reluctantly, I have to go with a python symlink. Out of the more
> >> > than 48000 tests in clang-11.0, one uses /usr/bin/env/python.
> >> >
> >>
> >> When we find something like that, couldn't we use:
> >> grep -rl '#!.*python' | xargs sed -i
> >> '1{s/python$/python3/;s/python[^3]/python3}'
> >>
> >> or so?
> >> Of course, P2 only scripts would still fail, but at least, nothing
> >> would depend on a python symlink.
> >>
> >> Pierre
> >>
> >I think the problem is more that using env python is hidden deep
> >within a lot of packages.
> >
>
> This _should_ go away on its own eventually. You are supposed to specify the
> major version. If a particular script doesn't, it is broken. Opening bugs for
> these errors upstream is entirely appropriate.
>
> --DJ
>
Is there an official python recommendation for that, to quote at
them, please ?
ĸen
--
The people next door oppress me all night long. I tell them: I work
all day, a man's got to have some time to learn to play the tuba.
That's oppression, that is. [ Guards! Guards! ]
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
