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 ) id 1NvDZc-0003MM-AO for garchives@archives.gentoo.org; Fri, 26 Mar 2010 17:43:56 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D2CA9E09CB; Fri, 26 Mar 2010 17:43:54 +0000 (UTC) Received: from mail-vw0-f53.google.com (mail-vw0-f53.google.com [209.85.212.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 4EC53E09A9 for ; Fri, 26 Mar 2010 17:43:47 +0000 (UTC) Received: by vws10 with SMTP id 10so324539vws.40 for ; Fri, 26 Mar 2010 10:43:47 -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=l5CtMPFM81JVNzyqKRllV07f6zSpiKHsOt8QgEn7y/M=; b=X7why0LqidP2jQNV/j1KWykuBaQ6zkWExz1QvsuP8u5HAaDjjEiKsTpgLyxCJEKJjs fzYwaAKr0p2fx/fAUl5k1RCQpnkOSzC5QFaj05sdasW7Ox/JkndKTNpgRrO6ooPd+8js HveHjzVES2oMM5EO9JdEyXUuvYZopEo+pi0uI= 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=fipQSUZZvCTImcTeG3+L3gz1BZ8k/v+9FUmZu88MO5/58KnW2kUMr5+CvQ2wQzBXWJ W6q1w4k7vLDb9DvN6lBc9XR806c2K9yp2Mwccfe9pODcBYEP6jXWj1J0XkXsCoSTFbVU /ez/N868wp0jHkoqF1OfhNYNZUNdfK8cbfZJk= Received: by 10.220.116.129 with SMTP id m1mr836052vcq.127.1269625426962; Fri, 26 Mar 2010 10:43:46 -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 25sm25664253vws.1.2010.03.26.10.43.44 (version=SSLv3 cipher=RC4-MD5); Fri, 26 Mar 2010 10:43:45 -0700 (PDT) Message-ID: <4BACF24E.1000800@gmail.com> Date: Fri, 26 Mar 2010 12:43:42 -0500 From: Dale 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: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail 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> <4BACDBFC.70706@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Archives-Salt: be4c3956-e231-4d63-865e-a25fb900305a X-Archives-Hash: fc074135d20ff23166991b05e783beb9 Alec Warner wrote: > On Fri, Mar 26, 2010 at 4:08 PM, Dale wrote: > =20 >> Arfrever Frehtes Taifersar Arahesis wrote: >> =20 >>> 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, loo= k >>>> 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 previo= us >>> 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 th= ere >> will be quite a few that will see python being updated, run python-upd= ater >> and switch it to the new python. At that point, it is going to hit th= e fan. >> I know because this is what I always do. News item or not, when pyt= hon >> gets updated, I run python-updater and make sure it is selected. >> =20 > 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.) > =20 root@smoker ~ # eselect python list Available Python interpreters: [1] python2.6 * [2] python3.1 root@smoker ~ # eselect python set 2 root@smoker ~ # eselect python list Available Python interpreters: [1] python2.6 [2] python3.1 * root@smoker ~ # That was pretty easy to select the new python. Everything I did was=20 right there. Two commands and it is switched. This is where problems=20 will start. > =20 >> If this somehow breaks portage, which it shouldn't since apparently po= rtage >> 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. Then I'm goi= ng to >> sit back and see what happens, good or bad. I can't imagine anything = good >> but I sure can imagine bad things. >> =20 > Such faith ;) > > =20 >> Dale >> >> :-) :-) >> >> >> =20 It's not faith, its reality. There will be some people that don't=20 subscribe to this list that will do what is above. This IS the reason I=20 subscribed to this list. I wanted to know what the devs were doing=20 under the hood that would lead me to screw up my system. It's amazing=20 how much fewer problems I have had since I started watching this list. Also, if python3 is marked as "stable," people will assume it is safe to=20 switch to. That's what "stable" means. Back to my hole. Dale :-) :-)