From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Enge <andreas@enge.fr>
Subject: Re: Python 3 native-search-paths
Date: Sun, 1 Sep 2013 15:41:02 +0200
Message-ID: <20130901134102.GA5340@debian>
References: <20130831154014.GA5736@debian> <87wqn1sv20.fsf@gnu.org>
	<20130831164305.GA9597@debian> <8761ulspjp.fsf@gnu.org>
	<20130901071112.GA7907@debian> <877gf0r7lq.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41585)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1VG7v9-0007oT-HZ
	for guix-devel@gnu.org; Sun, 01 Sep 2013 09:42:35 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1VG7v0-0003ny-1H
	for guix-devel@gnu.org; Sun, 01 Sep 2013 09:42:27 -0400
Received: from moutng.kundenserver.de ([212.227.126.186]:58454)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1VG7uz-0003ns-Ox
	for guix-devel@gnu.org; Sun, 01 Sep 2013 09:42:17 -0400
Resent-Message-ID: <20130901134213.GA5855@debian>
Resent-To: guix-devel@gnu.org
Content-Disposition: inline
In-Reply-To: <877gf0r7lq.fsf@gnu.org>
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: Ludovic =?iso-8859-15?Q?Court=E8s?= <ludo@gnu.org>

On Sun, Sep 01, 2013 at 03:31:45PM +0200, Ludovic Courtès wrote:
> When ‘native-search-paths’ changes in python3, it’s not python3 that
> behaves differently: it’s the build process of packages using it that
> does.

Not really. Then the output of, say, pytz, will change when the
native-search-paths of python changes, no? So we would obtain a pytz package
which is binary different, but has the same hash?

Andreas