On Mon, 30 Jul 2012 09:07:17 -0500 Matthew Summers wrote: > On Jul 30, 2012 9:04 AM, "Michał Górny" wrote: > > > > On Mon, 30 Jul 2012 08:11:09 -0500 > > Matthew Summers wrote: > > > > > On Mon, Jul 30, 2012 at 6:56 AM, Dirkjan Ochtman > > > wrote: > > > > > > > On Mon, Jul 30, 2012 at 11:50 AM, Michał Górny > > > > wrote: > > > > > Portage will pull python3 if and only if anything depends on > > > > > python:3.* or anything depends on python without a SLOT (or > > > > > either is in @world). If you want it not there, you have to > > > > > make sure the deps explicitly state it. > > > > > > > > So how did python3 end up in the stages again, exactly? > > > > > > > > Cheers, > > > > > > > > Dirkjan > > > > > > > > > > > Dirkjan, I believe it is portage that pulls in python:3, since by > > > default it prefers the latest stable version. > > > > No. As you can see in the ebuild, it pulls python2 by default. To > > pull in python3, you have to USE=python3. > > > > -- > > Best regards, > > Michał Górny > > So, what happens when you have neither USE python2 or python3 set, as > that is the default. I think that pulls in the latest stable version. Ah, sorry, my bad. I took '-2.7' for ':2.7'. Then you are indeed right. -- Best regards, Michał Górny