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 AE2621389E2 for ; Sun, 30 Nov 2014 21:02:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 333BDE08BB; Sun, 30 Nov 2014 21:02:41 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C844BE08BB for ; Sun, 30 Nov 2014 21:02:40 +0000 (UTC) Received: from mail-ig0-f179.google.com (mail-ig0-f179.google.com [209.85.213.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id B1DD2340042 for ; Sun, 30 Nov 2014 21:02:39 +0000 (UTC) Received: by mail-ig0-f179.google.com with SMTP id r2so7847518igi.0 for ; Sun, 30 Nov 2014 13:02:35 -0800 (PST) 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 X-Received: by 10.50.4.6 with SMTP id g6mr4239714igg.1.1417381355896; Sun, 30 Nov 2014 13:02:35 -0800 (PST) Received: by 10.64.111.132 with HTTP; Sun, 30 Nov 2014 13:02:35 -0800 (PST) In-Reply-To: <20141130215031.2b183cdf@pomiot.lan> References: <20141128235927.771a6e8b@pomiot.lan> <20141130215031.2b183cdf@pomiot.lan> Date: Sun, 30 Nov 2014 16:02:35 -0500 Message-ID: Subject: Re: [gentoo-python] Re: The future of PYTHON_SINGLE_TARGET From: Mike Gilbert To: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= Cc: gentoo-python , Gentoo Python Project Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 491a48f7-34b5-44cd-95ce-115b2ec99d6e X-Archives-Hash: b5b6ba559800580db56a73a7ccbf0003 On Sun, Nov 30, 2014 at 3:50 PM, Micha=C5=82 G=C3=B3rny = wrote: >> > B. they cause issues with REQUIRED_USE on other packages (like libpeas >> > that supports only one version of python2 and one of python3). Even >> > though PYTHON_SINGLE_TARGET results in effective use of a single impl, >> > PYTHON_TARGET USE-dep requests full PYTHON_TARGETS match on the dep. >> > Therefore, the user needs to disable other implementations anyway to >> > get the expected result. >> >> I don't understand this part. Can you please explain it? Maybe an exampl= e? > > gedit and libpeas, with gedit depending on libpeas. libpeas supports > one version of Python 2 and one of Python 3, and gedit just one > in general: > > libpeas is REQUIRED_USE=3D?? ( 2.* ) ?? ( 3.* ) > gedit is REQUIRED_USE=3D^^ ( 3.* ) > > So libpeas needs python-r1 with specific REQUIRED_USE. gedit would be > a candidate for python-single-r1 but... > > p-s-r1 enforces ^^ only on PYTHON_SINGLE_TARGET. So I end up with > something like: > > PYTHON_TARGETS=3D"3.3 3.4" PYTHON_SINGLE_TARGET=3D"3.4" > > and this enforces dependency on libpeas[3.3,3.4] which contradicts its > REQUIRED_USE. So we need also REQUIRED_USE=3D^^ ( 3.* ). But basically, > the whole mess with the second variable doesn't really help here. > What I take away from this is that the libpeas ebuild is really weird: supporting exactly one python2 and one python3 sounds like a horrible hack that should be fixed. I don't think this crazy REQUIRED_USE constraint is something we should design for in the eclasses. Let's fix libpeas to work with multiple python3 versions instead.