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 8A816138010 for ; Mon, 29 Oct 2012 21:50:02 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2367421C08F; Mon, 29 Oct 2012 21:49:53 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id D6D1F21C018 for ; Mon, 29 Oct 2012 21:49:24 +0000 (UTC) Received: from pomiocik.lan (213-238-96-169.adsl.inetia.pl [213.238.96.169]) (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 50D6F33D895; Mon, 29 Oct 2012 21:49:23 +0000 (UTC) Date: Mon, 29 Oct 2012 22:50:09 +0100 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-dev@lists.gentoo.org Cc: python@gentoo.org Subject: Re: [gentoo-dev] [RFC] A news item covering PYTHON_TARGETS Message-ID: <20121029225009.6f48409d@pomiocik.lan> In-Reply-To: <20121029154501.2c8d77dc@pomiocik.lan> References: <20121029154501.2c8d77dc@pomiocik.lan> Organization: Gentoo X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) 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-SHA256; boundary="Sig_/uwIutr1g6FoMWM1feHLPZjK"; protocol="application/pgp-signature" X-Archives-Salt: a5c44b1b-61ac-4c72-bec3-c7dac4de0081 X-Archives-Hash: 4402d16abf3afe438d099632539972b4 --Sig_/uwIutr1g6FoMWM1feHLPZjK Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, 29 Oct 2012 15:45:01 +0100 Micha=C5=82 G=C3=B3rny wrote: > Since some ebuilds are using that variable already and we still didn't > inform most of our users if and how they should set it, I'd like to > commit the following news item: Thank you for all your suggestions, and especially Duncan for wording the hardest paragraph for me ;). I've also tried to make the remaining ones clearer. Title: PYTHON_TARGETS deployment Author: Micha=C5=82 G=C3=B3rny Content-Type: text/plain Posted: 2012-10-29 Revision: 1 News-Item-Format: 1.0 Recently, a few new Python eclasses were deployed. As ebuilds migrate, the way they support multiple Python implementations will change. The previous method built Python modules for all currently installed Python implementations. The new one uses the PYTHON_TARGETS USE flags to explicitly name the implementations the modules shall be built for. If you are running a modern system with Python 2.7 & 3.2 being the only installed Python implementations, then you don't have to do anything. The defaults will simply fit you, and let you keep your system up-to-date when new Python versions are deployed. However, if you'd like to use another set of Python implementations, you will want to set PYTHON_TARGETS in your make.conf file appropriately. This variable names the enabled implementations in the standard way common to all USE_EXPAND variables. For example, a setup enabling all major Python implementations would look like: PYTHON_TARGETS=3D"python2_7 python3_2 pypy1_9 jython2_5" The variable should list all Python implementations which are going to be used on the system; missing a particular value there will result in missing Python modules. A complete list of all possible values can be obtained using a command equivalent to the following: emerge -1pv dev-python/python-exec --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/uwIutr1g6FoMWM1feHLPZjK Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iJwEAQEIAAYFAlCO+hIACgkQfXuS5UK5QB1f6gQAoRwpKKeUXANbXP70r43JMJHf 64GPiV4//zxi5CdDIMF6zcjsAJyh6Df6va+wcYfp87pPOqpBPtkFcukr2XXEXkcH WinWMZs9kb2VGVH7R8lTbSPJum5f/4qiUBw4KqDRn7+rXy0v2HU5G0dlLvOUHA+t m8M4WFBMQmEUeTn+sJM= =NF8E -----END PGP SIGNATURE----- --Sig_/uwIutr1g6FoMWM1feHLPZjK--