My system is configured with python-3.5 as default. libpeas require only one of the python 3s as target. Several gnome packages like gedit require python targets like libpeas. So I have them all -python3_3 -python3_4 python3_5. When I set totem -python3_3 -python3_4 python3_5 says it needs python3_4 target enabled in libpeas. If I change everything to +python3_4 -python3_5 then gnome-music requires the python3_5 target. The only workaround I have found is to disable the python use flag in totem.
Could you please add the portage output? Both totem and libpeas appear to have python3_5 support.
I solved the issue by disabling the python3_4 target in totem. There is too much playing around with python targets.
the issue is that if you have totem python_targets set to python3_4 python3_5 and libpeas python_targets set to -python3_4 python3_5 then totem wants libpeas flags changed -python3_4 -> +python3_4 That appears to be a bug. changing totem python_targets to -python3_4 works around the issue. Python should be able to use the libpeas python3_5 support and not call for a change to libpeas based on both 3.4 and 3.5 enabled as targets. If totem really needs libpeas support for each 3.x target that it should be restricted to the same use flags as libpeas and require only one 3.x python matching libpeas.
