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 8CCC113800E for ; Mon, 30 Jul 2012 02:13:34 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 597F9E050C; Mon, 30 Jul 2012 02:13:30 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 1F1D5E050C for ; Mon, 30 Jul 2012 02:13:30 +0000 (UTC) Received: from [192.168.1.204] (76-230-137-203.lightspeed.livnmi.sbcglobal.net [76.230.137.203]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id 792EB1B4005 for ; Mon, 30 Jul 2012 02:13:29 +0000 (UTC) Message-ID: <5015EDC2.202@gentoo.org> Date: Sun, 29 Jul 2012 22:13:22 -0400 From: Mike Gilbert User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120720 Thunderbird/14.0 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 Subject: [gentoo-python] Python 3 in Gentoo X-Enigmail-Version: 1.5a1pre Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enigB8DD87426C35059AEC238794" X-Archives-Salt: 528904b7-95bb-42ce-b8f2-10607928f213 X-Archives-Hash: bbb6e5615af27d00b2b6bd7e30fb521a This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB8DD87426C35059AEC238794 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: 1. Python 3.2 is installed by default on major arches due to its presence in the stage3 tarball. 2. Python 2 is NOT installed by default as nothing in the system set actually depends on it. 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. 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. I don't think this makes for a very good user experience. So, how can we change that? 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. 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 out= =2E We can work out the technical details in follow-up discussion. Is anyone in favor or opposed to this package rename idea? Are there any better ideas? --------------enigB8DD87426C35059AEC238794 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) iF4EAREIAAYFAlAV7ccACgkQC77qH+pIQ6SqDgD+OeOq5W6iibnZ47XUCUEMVi8y CLtoTUcOoGkVGRmcoscBALss7JaAPeJXCb8MvMMUWDH+CnYPh/OcufzZ6oi1kLNH =R9jw -----END PGP SIGNATURE----- --------------enigB8DD87426C35059AEC238794--