From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: 'python-build-system' Date: Thu, 09 May 2013 22:29:28 +0200 Message-ID: <878v3nx5g7.fsf@gnu.org> References: <87sj34zvn1.fsf@karetnikov.org> <87ehdwkntv.fsf@gnu.org> <87sj2b8llf.fsf@karetnikov.org> <877gjmr2to.fsf@karetnikov.org> <87ip36gyxz.fsf@gnu.org> <87obcym1vj.fsf@karetnikov.org> <871u9tlfzx.fsf@gnu.org> <87ppx2qlu8.fsf@karetnikov.org> <87k3n9zaea.fsf@gnu.org> <87y5bpys3h.fsf@karetnikov.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:51439) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UaXTB-0003zY-4l for bug-guix@gnu.org; Thu, 09 May 2013 16:29:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UaXT9-0000wp-QW for bug-guix@gnu.org; Thu, 09 May 2013 16:29:41 -0400 Received: from [2a01:e0b:1:123:ca0a:a9ff:fe03:271e] (port=54318 helo=xanadu.aquilenet.fr) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UaXT9-0000uS-Ko for bug-guix@gnu.org; Thu, 09 May 2013 16:29:39 -0400 In-Reply-To: <87y5bpys3h.fsf@karetnikov.org> (Nikita Karetnikov's message of "Thu, 09 May 2013 03:22:42 +0400") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Nikita Karetnikov Cc: bug-guix@gnu.org Nikita Karetnikov skribis: >> With these changes in place, OK to commit. > > I've just pushed both patches. Please have a look. > >> To answer your previous question, this =E2=80=98wrap=E2=80=99 phase serv= es a different >> (but related) purpose than the =E2=80=98native-search-paths=E2=80=99 thi= ng: it ensures >> that the =E2=80=98bzr=E2=80=99 program, when run by the user, finds all = its Python >> modules. > > I know. But why do we need to use 'native-search-paths' to set > PYTHONPATH if we wrap all executables anyway? What is the purpose of > 'native-search-paths' in this case? Not all Python packages have binaries, and when they do, they can often be used either as stand-alone binaries or as Python modules. Does that clarify? Ludo=E2=80=99.