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