| 1 |
On Friday 05 Dec 2014 09:27:49 Alec Ten Harmsel wrote: |
| 2 |
> On 12/05/2014 04:23 AM, Mick wrote: |
| 3 |
> > I have selected python 3.4 set with eselect: |
| 4 |
> > |
| 5 |
> > eselect python list |
| 6 |
> > |
| 7 |
> > Available Python interpreters: |
| 8 |
> > [1] python2.7 |
| 9 |
> > [2] python3.3 |
| 10 |
> > [3] python3.4 * |
| 11 |
> |
| 12 |
> afaik eselect means nothing to portage's dependency solver. |
| 13 |
|
| 14 |
Oh! I hadn't understood this correctly. |
| 15 |
|
| 16 |
|
| 17 |
> A couple things: |
| 18 |
> |
| 19 |
> * Do you have python3_4 in PYTHON_TARGETS? |
| 20 |
> * Do you have dev-lang/python:3.4 in @world? |
| 21 |
> |
| 22 |
> Basically, if you haven't explicitly let portage know you want python |
| 23 |
> 3.4, it will be depcleaned. |
| 24 |
|
| 25 |
I don't have python in world, because it is always installed as a dependency. |
| 26 |
However, I just noticed this in 'emerge --info': |
| 27 |
|
| 28 |
PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_3" |
| 29 |
|
| 30 |
Hmm ... if I don't have PYTHON_TARGETS in my make.conf, where else is this |
| 31 |
being set? |
| 32 |
|
| 33 |
-- |
| 34 |
Regards, |
| 35 |
Mick |
Archives