On Sun, Oct 12, 2014 at 11:26 AM, Frank Steinmetzger <[email protected]> wrote: > On Sat, Oct 11, 2014 at 07:37:42PM -0400, Philip Webb wrote: >> 141011 James wrote: >> > Philip Webb <purslow <at> ca.inter.net> writes: >> >> I've just installed python-3.4.1 alongside 2.7.7 3.2.5-r6 3.3.5-r1 . >> >> I've changed the lines in make.conf to >> >> USE_PYTHON="2.7 3.4" >> >> PYTHON_TARGETS="python2_7 python3_4" >> >> PYTHON_SINGLE_TARGET="python2_7" >> > I use 'eselect python list' to see what options you have. >> >> Google found : http://www.odi.ch/weblog/posting.php?posting=674 , >> which suggests that, then 'eselect python set --python3 <n>', >> where n = 3 in my case ; I've done that. >> >> > Then I'd poke around for any bug reports on python-3.4.* >> >> That promises to be time-consuming, but thanks so far. >> >> Anyone else have info or suggestions ? > > I noticed the same. I’m somewhat eager about python 3.4 because blender > always wants the beedingest edgiest stuff around, and blender 2.7x requires > python 3.4, which in turn even wants me to unmask python-exec 2.9999. > > Could this be profile induced? I do have PYTHON_TARGETS="python2_7 python3_3 > python3_4" in make.conf, yet `emerge --info | grep TARGETS` still tells me > PYTHON_TARGETS="python2_7 python3_3" >
At the moment, the python_target_python3_4 use flag is "stable-masked" while the necessary packages are being stabilized. I know this is a bit confusing, but it should not break anything. You can continue using python3.3 for a while if you like. For reference, see the following. profiles/base/use.stable.mask https://bugs.gentoo.org/show_bug.cgi?id=522322 https://bugs.gentoo.org/show_bug.cgi?id=524416 Once the stablereq bugs are resolved, I will remove the entry from use.stable.mask. In the meantime, you can unmask the pytho3_4 flag locally by creating the following entries in /etc/portage. mkdir -p /etc/portage/profile echo 5 > /etc/portage/profile/eapi echo -python_targets_python3_4 >> /etc/portage/profile/use.stable.mask
