On Sunday, 7 March 2021 17:03:22 GMT Arve Barsnes wrote:
> On Sun, 7 Mar 2021 at 17:00, Steven Lembark <lembark@wrkhors.com> wrote:
> > I believe there isn't any PYTHON_TARGET-ish setting on the system:
> >      $ grep PYTHON_TARGET /etc/portage/make.conf
> >      /etc/portage/package.use/*
> >     
> >     /etc/portage/make.conf:#PYTHON_TARGETS="python3_7 python2_7"
> >     /etc/portage/package.use/dizzy:#*/* PYTHON_TARGETS: python3_6
> >     python3_7
> >     /etc/portage/package.use/dizzy~:#*/* PYTHON_TARGETS: python3_6
> >     python3_7
> 
> What this is telling you is that you have no manual *override* of the
> default python target setting. Check yours with something like:
> $ emerge --info | grep PYTHON_TARGETS
> 
> The default at the moment is 3.8, and as eselect showed you, your
> default python interpreter is 3.9. Did you set this explicitly? If you
> have no particular need to move to 3.9 early, you could set 3.8 as the
> default and probably be rid of your problems immediately.
> 
> > Q: Is this related to the fact that I'm not actually checking
> > 
> >    python but a wrapper named "python-exec2c":
> >     $ ls -l /usr/bin/python3
> >     lrwxrwxrwx 1 root root 13 Oct 20 10:46 /usr/bin/python3 ->
> >     python-exec2c
> >    
> >    i.e., could the wrapper be mis-diagnosing the correct python
> >    version at install time?
> 
> It is finding python 3.9, which your system has set up to be the
> wanted version. The link is the same on my system, but I have 3.8 as
> my default interpreter, so I would not have these problems.
> 
> Regards,
> Arve

While eselect python is still available the OP can run:

eselect python update
eselect python cleanup