| 1 |
On Sat, Oct 11, 2014 at 07:37:42PM -0400, Philip Webb wrote: |
| 2 |
> 141011 James wrote: |
| 3 |
> > Philip Webb <purslow <at> ca.inter.net> writes: |
| 4 |
> >> I've just installed python-3.4.1 alongside 2.7.7 3.2.5-r6 3.3.5-r1 . |
| 5 |
> >> I've changed the lines in make.conf to |
| 6 |
> >> USE_PYTHON="2.7 3.4" |
| 7 |
> >> PYTHON_TARGETS="python2_7 python3_4" |
| 8 |
> >> PYTHON_SINGLE_TARGET="python2_7" |
| 9 |
> > I use 'eselect python list' to see what options you have. |
| 10 |
> |
| 11 |
> Google found : http://www.odi.ch/weblog/posting.php?posting=674 , |
| 12 |
> which suggests that, then 'eselect python set --python3 <n>', |
| 13 |
> where n = 3 in my case ; I've done that. |
| 14 |
> |
| 15 |
> > Then I'd poke around for any bug reports on python-3.4.* |
| 16 |
> |
| 17 |
> That promises to be time-consuming, but thanks so far. |
| 18 |
> |
| 19 |
> Anyone else have info or suggestions ? |
| 20 |
|
| 21 |
I noticed the same. I’m somewhat eager about python 3.4 because blender |
| 22 |
always wants the beedingest edgiest stuff around, and blender 2.7x requires |
| 23 |
python 3.4, which in turn even wants me to unmask python-exec 2.9999. |
| 24 |
|
| 25 |
Could this be profile induced? I do have PYTHON_TARGETS="python2_7 python3_3 |
| 26 |
python3_4" in make.conf, yet `emerge --info | grep TARGETS` still tells me |
| 27 |
PYTHON_TARGETS="python2_7 python3_3" |
| 28 |
|
| 29 |
-- |
| 30 |
Gruß | Greetings | Qapla’ |
| 31 |
Please do not share anything from, with or about me with any Facebook service. |
| 32 |
|
| 33 |
“I’m working on than.” -- Stephen Hawking |
| 34 |
(When visiting the set of the Starship Enterprise’s engine room) |
Archives