| 1 |
Probably you still have set PYTHON_TARGETS in your make.conf? |
| 2 |
I currently have no Gentoo system running so I can't check. |
| 3 |
|
| 4 |
|
| 5 |
On Fri Jun 19 15:19:50 2020, William Kenworthy <billk@×××××××××.au> wrote: |
| 6 |
> I have been slowly fixing the mess that the python upgrade has made of |
| 7 |
> my systems and have come across this: |
| 8 |
> |
| 9 |
> san0 ~ # eselect python list |
| 10 |
> Available Python interpreters, in order of preference: |
| 11 |
> [1] python3.6 |
| 12 |
> [2] python2.7 |
| 13 |
> san0 ~ # equery l python |
| 14 |
> * Searching for python ... |
| 15 |
> [IP-] [ ] dev-lang/python-2.7.18:2.7 |
| 16 |
> [IP-] [ ] dev-lang/python-3.6.10-r2:3.6/3.6m |
| 17 |
> [IP-] [ ] dev-lang/python-3.7.7-r2:3.7/3.7m |
| 18 |
> [IP-] [ ] dev-lang/python-3.8.2-r2:3.8 |
| 19 |
> san0 ~ # |
| 20 |
> |
| 21 |
> eselect python cleanup does not change anything. The system is refusing |
| 22 |
> me from removing python3.6 and re-emerging 3.7 doesn't change anything. |
| 23 |
> 4 other almost identical hosts are fine. |
| 24 |
> |
| 25 |
> I was looking at why ansible was failing on hosts that had python3.6 |
| 26 |
> removed and came across this one ... |
| 27 |
> |
| 28 |
> BillK |
| 29 |
> |
| 30 |
> |
| 31 |
> |
| 32 |
> |
| 33 |
> |
Archives