On Jul 30, 2012 9:11 AM, "Matthew Summers" <quantumsummers@gentoo.org> wrote:
>
> On Mon, Jul 30, 2012 at 6:56 AM, Dirkjan Ochtman <djc@gentoo.org> wrote:
>>
>> On Mon, Jul 30, 2012 at 11:50 AM, Michał Górny <mgorny@gentoo.org> 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.

IIRC, the only package that pulls python in is portage. And python 3 is being pulled as it is the latest version available in a slotted package that can be installed depending on both slots.

I believe we are past the point of no return in transforming python:3 into dev-lang/python3 as this is going to break things and make life harder for the python team.

Doesn't portage have a python3 useflag? Can't we change the default behavior on that flag to (or unset it in catalyst) to make it prefer python2?

>
> --
> Matthew W. Summers
> Gentoo Foundation Inc.
>