From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Python: inputs vs. propagated inputs Date: Mon, 03 Oct 2016 18:13:45 +0200 Message-ID: <87wphp8l6u.fsf@gnu.org> References: <67bb3997-bb9a-6699-1dca-d14889e8eefe@crazy-compilers.com> <87r38gmiyd.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36540) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1br5sH-0003se-Nq for guix-devel@gnu.org; Mon, 03 Oct 2016 12:13:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1br5sD-0004lH-0l for guix-devel@gnu.org; Mon, 03 Oct 2016 12:13:53 -0400 In-Reply-To: <87r38gmiyd.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 19 Sep 2016 09:45:14 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: Guix-devel Hi, Ricardo Wurmus skribis: > Hartmut Goebel writes: > >> Hi, >> >> I still do not get whether python packages required at run-time need to >> be inputs or propagated inputs. >> >> The part about inputs, native-inputs and propagated-inputs in section >> "package Reference" explicitly states Python as an example where >> propagated-inputs are needed. Neither the section about the >> python-build-system nor the python packaging guidelines give any other >> hints. >> >> In gnu/packages/python.scm there are modules using only inputs (e.g. >> python-ccm), some are using propagated-inputs (e.g. >> python-scikit-image), some using both (e.g. python-paramiko). I can not >> see any clear rule being followed. > > I=E2=80=99d say =E2=80=9Cpython-ccm=E2=80=9D is wrong (not only in using = =E2=80=9Cinputs=E2=80=9D but also in > its description). > > The exception are Python *applications*. Those usually have a wrapper > to set the PYTHONPATH appropriately. For Python modules we need > propagated-inputs for everything that must be available at runtime. I concur. Hartmut: if you have ideas on how to clarify this in the manual, that would be welcome! Probably under =E2=80=9CPython Modules=E2=80=9D? Thanks, Ludo=E2=80=99.