From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hartmut Goebel Subject: Re: Should python-build-system packages have native-inputs? Date: Sat, 28 Apr 2018 11:01:20 +0200 Message-ID: <9766df40-5e91-577e-d2ed-195a1d8569fd@crazy-compilers.com> References: <874ljv7rk0.fsf@gmail.com> 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]:55726) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fCLjV-0007Xf-GF for guix-devel@gnu.org; Sat, 28 Apr 2018 05:01:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fCLjQ-0006eY-Ks for guix-devel@gnu.org; Sat, 28 Apr 2018 05:01:29 -0400 Received: from mail-out.m-online.net ([212.18.0.10]:56596) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fCLjQ-0006dI-Ag for guix-devel@gnu.org; Sat, 28 Apr 2018 05:01:24 -0400 Received: from frontend01.mail.m-online.net (unknown [192.168.8.182]) by mail-out.m-online.net (Postfix) with ESMTP id 40Y4Xx43WVz1qtFb for ; Sat, 28 Apr 2018 11:01:21 +0200 (CEST) Received: from localhost (dynscan1.mnet-online.de [192.168.6.70]) by mail.m-online.net (Postfix) with ESMTP id 40Y4Xx3xgrz1qqx2 for ; Sat, 28 Apr 2018 11:01:21 +0200 (CEST) Received: from mail.mnet-online.de ([192.168.8.182]) by localhost (dynscan1.mail.m-online.net [192.168.6.70]) (amavisd-new, port 10024) with ESMTP id FLPIxTbthobA for ; Sat, 28 Apr 2018 11:01:20 +0200 (CEST) Received: from hermia.goebel-consult.de (ppp-93-104-183-220.dynamic.mnet-online.de [93.104.183.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.mnet-online.de (Postfix) with ESMTPS for ; Sat, 28 Apr 2018 11:01:20 +0200 (CEST) Received: from [192.168.110.2] (lenashee.goebel-consult.de [192.168.110.2]) by hermia.goebel-consult.de (Postfix) with ESMTP id 5A4BD60439 for ; Sat, 28 Apr 2018 11:01:20 +0200 (CEST) In-Reply-To: <874ljv7rk0.fsf@gmail.com> Content-Language: en-US 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: guix-devel@gnu.org Am 28.04.2018 um 08:50 schrieb Chris Marusich: > * Should we change these native-inputs to inputs to prevent confusion? > I can personally vouch for the fact that the presence of native-input= s > in python-build-system packages confused the heck out of me at first!= =C2=A0 As Fis already wrote:=C2=A0 These native-inputs are for testing and shoul= dn't be installed in normal case. Please see "Python Modules" in the manual: Python packages required only at build time---e.g., those listed with the @code{setup_requires} keyword in @file{setup.py}---or only for testing---e.g., those in @code{tests_require}---go into @code{native-inputs}.=C2=A0 The rationale is that (1) they do not need to= be propagated because they are not needed at run time, and (2) in a cross-compilation context, it's the ``native'' input that we'd want. > * Are there any circumstances under which it actually WOULD make sense > to cross-compile a Python package? Of course: Pure-python packages should be able to be cross-compiled without any problems, sicne the bytes-code is the same for all platforms. And for extension modules it would allow compiling on a faster environment (e.g. x86 vs. ARMv4). (I was not aware of python packages are not cross-compiled, thus I can only guess the reason why this is not possible: Python distutils may not be able to *cross*-compile extension modules. Maybe we could work on this= =2E) --=20 Regards Hartmut Goebel | Hartmut Goebel | h.goebel@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |