1 |
On 2020.06.19 03:19, William Kenworthy wrote: |
2 |
> I have been slowly fixing the mess that the python upgrade has made of |
3 |
> my systems and have come across this: |
4 |
> |
5 |
> san0 ~ # eselect python list |
6 |
> Available Python interpreters, in order of preference: |
7 |
> [1] python3.6 |
8 |
> [2] python2.7 |
9 |
> san0 ~ # equery l python |
10 |
> * Searching for python ... |
11 |
> [IP-] [ ] dev-lang/python-2.7.18:2.7 |
12 |
> [IP-] [ ] dev-lang/python-3.6.10-r2:3.6/3.6m |
13 |
> [IP-] [ ] dev-lang/python-3.7.7-r2:3.7/3.7m |
14 |
> [IP-] [ ] dev-lang/python-3.8.2-r2:3.8 |
15 |
> san0 ~ # |
16 |
> |
17 |
> eselect python cleanup does not change anything. The system is |
18 |
> refusing |
19 |
> me from removing python3.6 and re-emerging 3.7 doesn't change |
20 |
> anything. |
21 |
> 4 other almost identical hosts are fine. |
22 |
> |
23 |
> I was looking at why ansible was failing on hosts that had python3.6 |
24 |
> removed and came across this one ... |
25 |
> |
26 |
> BillK |
27 |
Any chance re-emerging eselect-python might help? |