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