On Sat, Dec 12, 2020 at 9:09 PM William Hubbs <willi...@gentoo.org> wrote: > > On Sat, Dec 12, 2020 at 04:25:48PM -0500, Mike Gilbert wrote: > > On Sat, Dec 12, 2020 at 3:48 PM William Hubbs <willi...@gentoo.org> wrote: > > > If both /usr/bin/python and /usr/bin/python3 are going away, the best > > > choice would be to add functionality to python-exec or eselect python to > > > tell us > > > the path to the default python interpretor. Once we know that we call it > > > directly. > > > > I don't think they are "going away". There is a USE flag on > > dev-lang/python-exec that makes them optional, and I think it will be > > forcibly enabled for the foreseeable future. > > > > > Please do not apply this patch to meson; I think we can figure something > > > out that is better. > > > > I think installing a small script to help translate arguments from one > > format to another is a reasonable solution. > > I think we should look at the eclass to see if we can provide functions > that can be used by consumers to handle this.
I don't really understand what you mean by this. I am converting one internal bash function into an external script so that its python dependencies can be better defined and managed. > Also, I don't think your script will run if native-symlinks is disabled since > in > that setting /usr/bin/python would not exist. python_doscript updates the shebang before installing the script. > I question the value of the native-symlinks use flag on python-exec > unless there is a way to query the path of the default python > interpretor. Regardless, I don't see how that makes my solution a bad thing. It ensures that the code will be executed by a known/support/tested version of python.
