Alan McKinnon <alan.mckinnon <at> gmail.com> writes:
> > Alan McKinnon <alan.mckinnon <at> gmail.com> writes: > >> emerge --info | grep PYTHON > > PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_4" > > USE_PYTHON > The solution is right there in the original output. The ebuild needs > 3_4, you have 2_7. So set it in USE. So you are saying the first output of that env parse is the default setting? I thought eselect set the priority:: # eselect python list Available Python interpreters: [1] python2.7 [2] python3.4 * If that's not true where do I got to set the default to 3.4? I.E. where is the best place to set that env varialble for python? Is it a system default that is not address by eselect? It was set up to python 3.4 by default, according to eselect. The openshot (EAPI-6) ebuild did not pick this up, automatically, so I set these falgs manually in ::/etc/portage/package.use/package.use:: media-video/openshot python_single_target_python3_4 dev-python/PyQt5 webkit gui widgets opengl network printsupport I view python 2.x and deprecated, hence I never want to set it as a default, ymmv. I guess it's a bug as I have not had problem with other python codes/ebuilds. I'd need some verification on the status as a bug to file with bgo. thx for all the help and comments to everyone. James
