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