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-37772-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1MpOLX-0003UK-D5
	for garchives@archives.gentoo.org; Sun, 20 Sep 2009 15:29:03 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id B0B40E085B;
	Sun, 20 Sep 2009 15:29:01 +0000 (UTC)
Received: from IMPaqm1.telefonica.net (impaqm1.telefonica.net [213.4.129.21])
	by pigeon.gentoo.org (Postfix) with ESMTP id 53EDCE085B
	for <gentoo-dev@lists.gentoo.org>; Sun, 20 Sep 2009 15:29:01 +0000 (UTC)
Received: from IMPmailhost6.adm.correo ([10.20.102.127])
	by IMPaqm1.telefonica.net with bizsmtp
	id j0F01c00S2kvMAa013V0B7; Sun, 20 Sep 2009 17:29:00 +0200
Received: from jesgue.homelinux.org ([78.136.66.163])
	by IMPmailhost6.adm.correo with BIZ IMP
	id j3UA1c0083XLmEe1m3UBUo; Sun, 20 Sep 2009 17:28:11 +0200
X-TE-authinfo: authemail="i92guboj.terra.es" |auth_email="i92guboj@terra.es"
X-TE-AcuTerraCos: auth_cuTerraCos="cosuitera01"
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
Date: Sun, 20 Sep 2009 17:28:58 +0200
From: =?UTF-8?Q?Jes=C3=BAs_Guerrero?= <i92guboj@terra.es>
To: <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Stabilization of Python 3.1
In-Reply-To: <200909201725.00070.Arfrever@gentoo.org>
References: <200909191848.33225.Arfrever@gentoo.org> <200909200041.32652.cla@gentoo.org> <19e69baf3d2d95babe2abc5f89c4322d@localhost> <200909201725.00070.Arfrever@gentoo.org>
Message-ID: <091be2b0c034b3e5d32a7d42caeefe76@localhost>
X-Sender: i92guboj@terra.es
User-Agent: RoundCube Webmail/0.3-stable
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: 47466570-1d64-492c-a973-97f6d5eaf412
X-Archives-Hash: 7b30aa9293edd6adec1d3020fd68cf09

On Sun, 20 Sep 2009 17:24:53 +0200, Arfrever Frehtes Taifersar Arahesis
<Arfrever@gentoo.org> wrote:
> 2009-09-20 16:53:37 Jes=C3=BAs Guerrero napisa=C5=82(a):
>> On Sun, 20 Sep 2009 00:41:32 +0200, Dawid W=C4=99gli=C5=84ski <cla@gen=
too.org>
>> wrote:
>> > On Sunday 20 of September 2009 00:32:28 Dale wrote:
>> >> >
>> >> > ~arch is for testing ebuilds, not the upstream package
>> >>
>> >> So it would be OK to mark something "stable" even tho portage itsel=
f
>> >> doesn't work with it?  Sorry, this makes no sense to me.  I run
stable
>> >> for the most part and having a package that portage depends on that
is
>> >> not stable just sounds a little like putting the cart before the
>> >> horse.
>> >>
>> >> See some of the other replies as to why this is a not so good idea.
>> >>
>> >> Dale
>> >>
>> >> :-)  :-)
>> >=20
>> > You mix it up. Portage works with python 3.1. If an user switches to
>> > python=20
>> > 3.1 as the main interpreter, it's possible that his own scripts won'=
t
>> > work.=20
>>=20
>> Yes?
>>=20
>> # eselect python set 2
>> # emerge -s foo
>>   File "/usr/bin/emerge", line 41
>>     except PermissionDenied, e:
>>                            ^
>> SyntaxError: invalid syntax
>>=20
>>=20
>> Ummm, yes, it works *beautifully*, you see. Nothing else to add.
>=20
> I have fixed it today :) .
> http://sources.gentoo.org/viewcvs.py/portage?rev=3D14289&view=3Drev
>=20
>> > Marking it stable sometine in november give's some time to ebuilds=20
>> > maintainers to fix their python based apps just like it's done with
>> > gcc
>> > stabilization.
>>=20
>> That's not the usual case. In Gentoo we have a serious policy of not
>> marking as stable things until it has passed one month without any
>> serious
>> bug report about it.
>=20
> There wasn't any serious bug report about Python 3.1.
> IIRC the only problem was a (already fixed) build failure caused by
> non-UTF-8
> characters in header of Berkeley DB.
> Stabilization of Python 3.1.1-r1 is planned over 1 month after its
> addition to
> the tree and about 3 months after addition of 3.1 slot to the tree.

That sounds better. :)

All users want is something that works out of the box. As long as that's
true I don't have a problem with the change. I myself live in ~arch for m=
y
desktop machine, I am just concerned about the average user.

--=20
Jes=C3=BAs Guerrero