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-40237-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1NvC5Y-0007Ow-6w
	for garchives@archives.gentoo.org; Fri, 26 Mar 2010 16:08:48 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 4269AE0B0A;
	Fri, 26 Mar 2010 16:08:45 +0000 (UTC)
Received: from mail-gy0-f181.google.com (mail-gy0-f181.google.com [209.85.160.181])
	by pigeon.gentoo.org (Postfix) with ESMTP id B347BE0AA5
	for <gentoo-dev@lists.gentoo.org>; Fri, 26 Mar 2010 16:08:31 +0000 (UTC)
Received: by gyh20 with SMTP id 20so4417895gyh.40
        for <gentoo-dev@lists.gentoo.org>; Fri, 26 Mar 2010 09:08:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from
         :user-agent:mime-version:to:subject:references:in-reply-to
         :content-type:content-transfer-encoding;
        bh=K2DlmtNDqQGYwUiWn8f/4Ih9hfNP/wlKfZr2wADp5xg=;
        b=nWZJ3+FtiB5k99Y4Xrb02xZokIpUlAl4sgbNS6WxeNZRSO9LfjeEOoMr7A6t2CfN5r
         H5eo5ZpkjqD+6TJGDrSu4tYH178P7Rb/TI5j01vEEVPVlKVde65UUdpqLR0L8Eg7hp8x
         CD8XxdrnDwBeMss+hfv+9QtSQ7jPgywsjdfmk=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=RFzeg7LdnICSMglw1v97LO4AhSAzJap9IVJ8KG3kN0m9utPH2GHmmCQuWLaU0ygUwm
         szh/DjsT1y3M97loxBv/+cl6eIzakYXImPQNNBvLQNiU8bGS4wYV1jpIEA6GytfkidrU
         8AoV+eQAbMjLtbdKG2geVFff+CZxYquX77JcM=
Received: by 10.91.55.17 with SMTP id h17mr786604agk.57.1269619711359;
        Fri, 26 Mar 2010 09:08:31 -0700 (PDT)
Received: from [192.168.1.2] (adsl-95-108-130.jan.bellsouth.net [98.95.108.130])
        by mx.google.com with ESMTPS id 13sm692150gxk.0.2010.03.26.09.08.29
        (version=SSLv3 cipher=RC4-MD5);
        Fri, 26 Mar 2010 09:08:29 -0700 (PDT)
Message-ID: <4BACDBFC.70706@gmail.com>
Date: Fri, 26 Mar 2010 11:08:28 -0500
From: Dale <rdalek1967@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100304 Gentoo/2.0.3 SeaMonkey/2.0.3
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
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Python 3.1: Stabilization and news item
References: <201003241814.45606.Arfrever@gentoo.org> <4BACAA07.90409@gentoo.org> <20100326154037.GB5254@hrair> <201003261657.23058.Arfrever@gentoo.org>
In-Reply-To: <201003261657.23058.Arfrever@gentoo.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 6623a31c-8828-433d-a631-4cef72be9e7b
X-Archives-Hash: 65a6b7bc77ff7f1fc75c8c75a0ce9e85

Arfrever Frehtes Taifersar Arahesis wrote:
> 2010-03-26 16:40:37 Brian Harring napisa=C5=82(a):
>   =20
>> 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.  If in doubt, look
>> at the past python upgrades- they've been delayed till all of the
>> major consumers played nice w/ the targeted python version.
>>     =20
> Main active version of Python was automatically updated during previous=
 Python
> upgrades, but it's not updated during installation of Python 3.1.
>
>   =20

As a user, I still think this could turn into a real mess.  I think=20
there will be quite a few that will see python being updated, run=20
python-updater and switch it to the new python.  At that point, it is=20
going to hit the fan.  I know because this is what I always do.  News=20
item or not, when python gets updated, I run python-updater and make=20
sure it is selected.

If this somehow breaks portage, which it shouldn't since apparently=20
portage is fine with the new python, then it is going to really hit the f=
an.

Me, I'm going to make SURE nothing changes on my system.  Then I'm going=20
to sit back and see what happens, good or bad.  I can't imagine anything=20
good but I sure can imagine bad things.

Dale

:-)  :-)