Re: The looming Python 3(000) monster

["Jon Ciesla" <limb jcomserv net>]

> Jon Ciesla wrote:
>> It's gonna hurt, and obviously we'll need a compat-python26, but I think
>> we'll be able to port things over, and have them either use Python3k or
>> compat- as needed.  Not sure when we'd be completely cut over, but I'd
>> love to see 2.6 the default in F11, which I believe is the plan, and
>> Py3k
>> in the not too distant future*, F12.
>>
> We're going to avoid compat-python26 if possible.  The reason is that
> third party modules are needed to make a program work.  So we wouldn't
> just have a python26 package.... we'd have python26, python26-mozilla,
> python26-libxml2, python26-pygtk, and etc.

I have to do this at work for 2.3, 2.4 and 2.5.  It SUCKS.  So I agree,
let's not. :)

> -Toshio
>
>


-- 
in your fear, speak only peace
in your fear, speak only love

-d. bowie