From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: Python 3 native-search-paths
Date: Sat, 31 Aug 2013 20:06:34 +0200
Message-ID: <8761ulspjp.fsf@gnu.org>
References: <20130831154014.GA5736@debian> <87wqn1sv20.fsf@gnu.org>
	<20130831164305.GA9597@debian>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:60509)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1VFpeB-0007d5-6D
	for guix-devel@gnu.org; Sat, 31 Aug 2013 14:11:49 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1VFpe4-0003Ou-So
	for guix-devel@gnu.org; Sat, 31 Aug 2013 14:11:43 -0400
Received: from hera.aquilenet.fr ([141.255.128.1]:57578)
	by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <ludo@gnu.org>)
	id 1VFpe4-0003Oq-MA
	for guix-devel@gnu.org; Sat, 31 Aug 2013 14:11:36 -0400
In-Reply-To: <20130831164305.GA9597@debian> (Andreas Enge's message of "Sat,
	31 Aug 2013 18:43:05 +0200")
List-Id: <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org

Andreas Enge <andreas@enge.fr> skribis:

> On Sat, Aug 31, 2013 at 06:07:35PM +0200, Ludovic Court=C3=A8s wrote:
>> Andreas Enge <andreas@enge.fr> skribis:
>> > I just noticed that there is a variable native-search-paths in python-=
2,
>> > which looks like it should be updated for python 3. However, when I mo=
dify
>> > the package accordingly, it is not recompiled. How come? Is this varia=
ble
>> > really needed?
>>=20
>> Yes it is [0].  :-)
>> Changing it triggers a recompilation of anything that depends on Python,
>> but not of Python itself.
>
> How can it trigger anything if the output path is identical
> (here: /nix/store/0hf9lvd48q1l98k5jf98z17zq29955c4-python-3.3.2)?

It has no effect in the build of Python itself; its effect is only when
building Python code that uses Python and one or more Python libs.

Ludo=E2=80=99.