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 549DD13800E for ; Mon, 30 Jul 2012 07:45:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8BE58E0552; Mon, 30 Jul 2012 07:45:03 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 5371AE0552 for ; Mon, 30 Jul 2012 07:45:03 +0000 (UTC) Received: from pomiocik.lan (87-205-56-136.adsl.inetia.pl [87.205.56.136]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id A6AD51B4008; Mon, 30 Jul 2012 07:45:01 +0000 (UTC) Date: Mon, 30 Jul 2012 09:45:19 +0200 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: Mike Gilbert Cc: gentoo-python Subject: Re: [gentoo-python] Python 3 in Gentoo Message-ID: <20120730094519.01c956af@pomiocik.lan> In-Reply-To: <5015EDC2.202@gentoo.org> References: <5015EDC2.202@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.11; x86_64-pc-linux-gnu) 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 Content-Type: multipart/signed; micalg=PGP-SHA256; boundary="Sig_/Ub_mkovwxbc/c9=3GXPkbHV"; protocol="application/pgp-signature" X-Archives-Salt: 0cb189e4-7310-4891-85b9-825b817664f4 X-Archives-Hash: 33262454d264f987e24e810e16946414 --Sig_/Ub_mkovwxbc/c9=3GXPkbHV Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sun, 29 Jul 2012 22:13:22 -0400 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 > we 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 we should not force users to unmask it. Portage is doing something like that? Paludis, yes, but portage - I doubt it. I'm pretty sure it shouldn't pull anything in unless something (*anything*) depends on python:3, or python without SLOT. Well, unless you're saying that very, very smart python.eclass have just built a lot of apps with semi-automagic dependency on python:3.* and you didn't rebuild them all without 3.* in USE_PYTHON. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/Ub_mkovwxbc/c9=3GXPkbHV Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iJwEAQEIAAYFAlAWO5QACgkQfXuS5UK5QB0HIAP6AkunsqEdnNNCbKaSxkYqnAwB bgHoq+zSeZuwCP2ag8dNt0l2GwFxtvE4BKGy/X9ufd7kEf6CORCnQZpsYBADNlZp b+M56kZJwdxdn6A35J6TgZPsPhNjkbL45bTekointHh+LxWTFsC5Gzg0aInP0pSW Kp/qQoKRE4+LWPeYXs0= =Hflk -----END PGP SIGNATURE----- --Sig_/Ub_mkovwxbc/c9=3GXPkbHV--