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 1NoJwN-0007kA-1o for garchives@archives.gentoo.org; Sun, 07 Mar 2010 17:06:55 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7C51EE076B; Sun, 7 Mar 2010 17:06:51 +0000 (UTC) Received: from rookery.halcy0n.com (rookery.halcy0n.com [69.72.242.50]) by pigeon.gentoo.org (Postfix) with ESMTP id D4021E072F for ; Sun, 7 Mar 2010 17:06:46 +0000 (UTC) Received: by rookery.halcy0n.com (Postfix, from userid 1000) id 3E319A5617; Sun, 7 Mar 2010 12:11:47 -0500 (EST) Date: Sun, 7 Mar 2010 12:11:47 -0500 From: Mark Loeser To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Python 3.1: Stabilization and news item Message-ID: <20100307171147.GL30005@halcy0n.com> References: <201003041923.17749.Arfrever@gentoo.org> <4B902321.4020906@gentoo.org> 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 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="y96v7rNg6HAoELs5" Content-Disposition: inline In-Reply-To: <4B902321.4020906@gentoo.org> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-Archives-Salt: 72d96555-a5c5-4f41-9223-2d7f918951c6 X-Archives-Hash: 642c04d73f514307c6e855ecba2dbd1f --y96v7rNg6HAoELs5 Content-Type: text/plain; charset=utf8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Sebastian Pipping said: > On 03/04/10 19:22, Arfrever Frehtes Taifersar Arahesis wrote: > > All problems, which were blocking stabilization of Python 3, have been = fixed. > > Stabilization of Python 3.1.2 is currently scheduled on 2010-04-19. >=20 > #python on Freenode still reads "It's too early to use Python 3.x". > Are they wrong? I'd believe them. > Are we at a point already where we can feed 90% of the Python 2.x code > out there to Python 3 without problems? Doesn't seem that way. > Has QA given their blessing to this? Absolutely not. Its actually the opposite. Until 90+% of the tree just works with the new version of python, it should not be stabilized. The stable tree should all Just Work together. Stabilizing python-3 at this point would be the equivalent of me stabilizing gcc-4.5 after its been in the tree for a few months and nothing else works with it. Sure, gcc works just fine, but it can't compile half of the tree. I hope everyone can see that this is a terrible idea and of no use to our stable users. If a stable user really needs Python-3, they will have the technical ability to unmask it and use it properly. --=20 Mark Loeser email - halcy0n AT gentoo DOT org email - mark AT halcy0n DOT com web - http://www.halcy0n.com --y96v7rNg6HAoELs5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFLk95TCRZPokWLroQRAluPAJ9HNC/IJTkNtdcuR4CWjepYO50bTwCgtIrI 3pbJiNpm+KxTBxGKfBEtxJk= =3DoA -----END PGP SIGNATURE----- --y96v7rNg6HAoELs5--