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 D0BB21381F3 for ; Sun, 20 Oct 2013 14:53:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AEB7CE09EE; Sun, 20 Oct 2013 14:53:37 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 246B3E0A83 for ; Sun, 20 Oct 2013 14:53:37 +0000 (UTC) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (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 4F28733EFDF for ; Sun, 20 Oct 2013 14:53:36 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id tp5so9805355ieb.31 for ; Sun, 20 Oct 2013 07:53:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=ecQXeVu6tU7/nlDW/vWfUHjUiezEy341UvtsTBF4zZY=; b=LtzrKZlOSYcLKqTAEPqv9UcHCJPQAk0AWZsZNVBhv7e3oOELsYxzq/NGG8up1YTuDf qoGk6IlE1AYsgSL2dMlQYpjkrDA+jGIRYvfXkq9BgSnLJsJiRj1l9LbGjX0pPEnL/5uQ R9R0GwcEf/pDE6PuuvnTjBHOtmkcgnkgxChYx6VXoDM692WsrGvrJnKQzKabQm7QM3UX LLfzkfudVSJAO7RdcIO/x2k9IYadKKHzFUtt3+Q5dfS9WE3t60zahDMjWqrNsxTpPSU+ WCGgxKZcRQ8DmfhOMq1f8+sf2to6WLws7+QzhN0Aeg3h6I3Ndu3UzjmITSTQ4lYxUfJB Xdug== 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.234.162 with SMTP id uf2mr6339302igc.48.1382280814322; Sun, 20 Oct 2013 07:53:34 -0700 (PDT) Received: by 10.64.139.5 with HTTP; Sun, 20 Oct 2013 07:53:34 -0700 (PDT) In-Reply-To: <1382254606-26643-1-git-send-email-mgorny@gentoo.org> References: <1382254606-26643-1-git-send-email-mgorny@gentoo.org> Date: Sun, 20 Oct 2013 10:53:34 -0400 Message-ID: Subject: Re: [gentoo-python] [PATCH] Introduce python_setup() as a common name for Python setup function. From: Mike Gilbert To: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= Cc: gentoo-python Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: ba81117a-35d3-448d-980b-5a1d097a489e X-Archives-Hash: c62d11a77583705169f5561df1078cc3 On Sun, Oct 20, 2013 at 3:36 AM, Micha=C5=82 G=C3=B3rny = wrote: > As described in the ml, the new function does: > > * in python-any-r1, choose and set up the best installed impl, > > * in python-single-r1, read PYTHON_SINGLE_TARGET and set it up, > > * in python-r1, call python_export_best + python_wrapper_setup. > > In other words, it's a common way of getting Python build environment > set up in the ebuild scope. Invoking python_setup from pkg_setup in any eclass seems sub-optimal; especially so in python-any-r1. However, I realize there isn't a great place to put it. Looks ok to me.