Why do you think emerge might be the issue? It's quite rare for portage itself to be causing problems with packages.
That said, if you have good reason to believe so you can adjust the
PYTHON_TARGETS for sys-apps/portage in /etc/portage/package.use like so:
sys-apps/portage PYTHON_TARGETS: +python3_6 -python3_7
Or you can keep both. You will of course need to rebuild portage
following this change.
Likewise, you use the syntax of the above entry to adjust the python
targets for any package.
Your default interpreter choice (as reported by eselect) is likely not
respected by portage because the current profile defaults only build
portage against python 3.7.
- Victor
On 16/05/2020 02:32, William Kenworthy wrote:
> How can I force emerge to use python 3.6 when 3.7 is installed? -
> eselect list shows 3.6 is #1 and 3.7 as fallback so that doesn't work.
>
> I am trying to narrow down a failure which appears to be a combination
> of building packages that are stored on a moosefs network share and
> python 3.7
>
> BillK
>
>
signature.asc
Description: OpenPGP digital signature
