From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-dev+bounces-40239-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1NvCOn-0001HV-CV
for garchives@archives.gentoo.org; Fri, 26 Mar 2010 16:28:41 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 63E8CE08E9;
Fri, 26 Mar 2010 16:28:37 +0000 (UTC)
Received: from mail-yx0-f181.google.com (mail-yx0-f181.google.com [209.85.210.181])
by pigeon.gentoo.org (Postfix) with ESMTP id A2156E08AC
for <gentoo-dev@lists.gentoo.org>; Fri, 26 Mar 2010 16:28:30 +0000 (UTC)
Received: by yxe11 with SMTP id 11so244518yxe.10
for <gentoo-dev@lists.gentoo.org>; Fri, 26 Mar 2010 09:28:30 -0700 (PDT)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Sender: antarus@scriptkitty.com
Received: by 10.100.247.17 with HTTP; Fri, 26 Mar 2010 09:28:29 -0700 (PDT)
In-Reply-To: <4BACDBFC.70706@gmail.com>
References: <201003241814.45606.Arfrever@gentoo.org>
<4BACAA07.90409@gentoo.org> <20100326154037.GB5254@hrair>
<201003261657.23058.Arfrever@gentoo.org> <4BACDBFC.70706@gmail.com>
Date: Fri, 26 Mar 2010 16:28:29 +0000
X-Google-Sender-Auth: 34adbbb0f2c20f1d
Received: by 10.101.169.39 with SMTP id w39mr1949777ano.140.1269620909961;
Fri, 26 Mar 2010 09:28:29 -0700 (PDT)
Message-ID: <r2ob41005391003260928z2b2fff78k86202c8c49434a8d@mail.gmail.com>
Subject: Re: [gentoo-dev] Python 3.1: Stabilization and news item
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: d5bce720-d29e-494e-883a-958ef386d2eb
X-Archives-Hash: 681648fbfe6485ae721918d7bca82c11
On Fri, Mar 26, 2010 at 4:08 PM, Dale <rdalek1967@gmail.com> wrote:
> Arfrever Frehtes Taifersar Arahesis wrote:
>>
>> 2010-03-26 16:40:37 Brian Harring napisa=C5=82(a):
>>
>>>
>>> There really isn't a precedent since upgrades of this sort typically
>>> either have extremely locked down deps, or just plain don't happen
>>> till the vast majority of depndencies are updated. =C2=A0If in doubt, l=
ook
>>> at the past python upgrades- they've been delayed till all of the
>>> major consumers played nice w/ the targeted python version.
>>>
>>
>> Main active version of Python was automatically updated during previous
>> Python
>> upgrades, but it's not updated during installation of Python 3.1.
>>
>>
>
> As a user, I still think this could turn into a real mess. =C2=A0I think =
there
> will be quite a few that will see python being updated, run python-update=
r
> and switch it to the new python. =C2=A0At that point, it is going to hit =
the fan.
> =C2=A0I know because this is what I always do. =C2=A0News item or not, wh=
en python
> gets updated, I run python-updater and make sure it is selected.
My assumption here is that eselect-python will not let you select v3
as your python version without some prodding (eg setting stupid
environment variables or similar.)
>
> If this somehow breaks portage, which it shouldn't since apparently porta=
ge
> is fine with the new python, then it is going to really hit the fan.
>
> Me, I'm going to make SURE nothing changes on my system. =C2=A0Then I'm g=
oing to
> sit back and see what happens, good or bad. =C2=A0I can't imagine anythin=
g good
> but I sure can imagine bad things.
Such faith ;)
>
> Dale
>
> :-) =C2=A0:-)
>
>