From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 7533913800E for ; Mon, 30 Jul 2012 02:25:45 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 71E92E06AF; Mon, 30 Jul 2012 02:25:42 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 28D65E06AF for ; Mon, 30 Jul 2012 02:25:42 +0000 (UTC) Received: from [192.168.1.2] (pool-72-89-250-138.nycmny.fios.verizon.net [72.89.250.138]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ryao) by smtp.gentoo.org (Postfix) with ESMTPSA id 8443C1B4008 for ; Mon, 30 Jul 2012 02:25:41 +0000 (UTC) Message-ID: <5015F023.1000903@gentoo.org> Date: Sun, 29 Jul 2012 22:23:31 -0400 From: Richard Yao User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120628 Thunderbird/10.0.5 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Discussions centering around the Python ecosystem in Gentoo Linux X-BeenThere: gentoo-python@gentoo.org X-BeenThere: gentoo-python@lists.gentoo.org MIME-Version: 1.0 To: gentoo-python@lists.gentoo.org Subject: Re: [gentoo-python] Python 3 in Gentoo References: <5015EDC2.202@gentoo.org> In-Reply-To: <5015EDC2.202@gentoo.org> X-Enigmail-Version: 1.3.5 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig8400F57812093928CF450413" X-Archives-Salt: 2c574843-26eb-48e0-a8a0-15fb6f5c9b68 X-Archives-Hash: aacc6414b35f57419d05cf48eb1f7ded This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8400F57812093928CF450413 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 07/29/2012 10:13 PM, Mike Gilbert wrote: > This past weekend, the topic of the current state of Python 3 in Gentoo= > was raised once again in the #gentoo-dev IRC channel. Here's where we > currently stand: >=20 > 1. Python 3.2 is installed by default on major arches due to its > presence in the stage3 tarball. >=20 > 2. Python 2 is NOT installed by default as nothing in the system set > actually depends on it. >=20 > 3. In most cases, users end up building and installing Python 2.7 as a > dependency of some other package once they have their system set up. > Users end up having two versions of Python installed. >=20 > This third point is the cause of some annoyance for several (many?) > developers and users. In most cases, there really is no reason for a > user to have two versions of Python installed; it is simply a redundant= > set of code. However, if you attempt to remove Python 3, portage will > just pull it back on the next world upgrade unless you mask it. >=20 > I don't think this makes for a very good user experience. So, how can w= e > change that? >=20 > As I see it, we need a way to avoid portage's overly optimistic upgrade= > mechanic. One way to do that is to drop the stable keywords on Python 3= , > but I feel that is dishonest; Python 3 itself is perfectly stable, so w= e > should not force users to unmask it. >=20 > The other way that occurs to me (and others) is to rename > dev-lang/python-3* to dev-lang/python3, treating it as an entirely > separate package. I believe this has been proposed in the past, and I'm= > honestly not sure why it never gained traction. It would take some work= , > but we have already had a couple of non-python devs volunteer to help o= ut. >=20 > We can work out the technical details in follow-up discussion. >=20 > Is anyone in favor or opposed to this package rename idea? Are there an= y > better ideas? >=20 I have already setup a github repository we could use to make the appropriate changes to the tree at our leisure: https://github.com/gentoo/portage-devel Then it should be possible to do this change with minimal disruption once we are happy with what we have there. Also, I am willing to help. :) --------------enig8400F57812093928CF450413 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQFfAkAAoJECDuEZm+6ExkRzkP/R/D0RZpbR7Vdodj+SqwWhCl tt2nIXndMSF13BBprM2o6CVsXXhKDcYXGxeWBB0xf012JqkfEXd42G7SA1COPXk7 8jtqhDSJ4OWJxWLVDDj0dJbffxFrfzOvnoPqee4te/VCq4fInx1VaVFaGLmlYi/l nAkEG5AWCnuOLdcKJ7UxugLy67PBBHQoUidLokSlMLIK6UU6Pbz6uDKEIonZMxF+ 8KYcVqWgtK9uFhUzMAv8Kr7TNQ8E90yMsuWVAVOBs92SlK+gLcbc5k8bScAKhMZl 1vpZDXgevyIvtbgjHsKJwqZ8qPMWpyVcufdpH2ReEQGahrlv3x3TJflRXBvPbNPk zkwD3iCWlinIcxqJrql/krDJavD8he1pmjy2YSVLidgILnirlB2iuIMp7XRb8B8+ 8DxPuOZBJ1Ll9EOMj5xs3gZmuJtyfoUJB6Zm20YUS1k5F1VNiVRKz5j/uvolJ4ox L10iF1cL1CuwOQvPCX7qYChqbCkMsx6WMv4Bo7qYwT1n9cSq9sZ0KxiG1+eR6rBw qhp91CHRDn40YvOEOArKCs/gYUO63ULFEY9MIqAVwEwE45tIYE5GfY5vqkW9m4PR n4GCvIP2XbUYCN2CLa3R+J/h4XAB/iNwQspYyky2maKFUUJF7Fet3d3ISCRHRSpk eUkVWgRf/fIGaUKmqEjs =59GV -----END PGP SIGNATURE----- --------------enig8400F57812093928CF450413--