From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Python 3 binaries Date: Sat, 31 Aug 2013 17:30:18 +0200 Message-ID: <20130831153018.GA5442@debian> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38494) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VFn8C-0004oB-2f for guix-devel@gnu.org; Sat, 31 Aug 2013 11:30:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VFn84-0007MF-ON for guix-devel@gnu.org; Sat, 31 Aug 2013 11:30:32 -0400 Received: from moutng.kundenserver.de ([212.227.17.9]:57753) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VFn84-0007Lz-Et for guix-devel@gnu.org; Sat, 31 Aug 2013 11:30:24 -0400 Content-Disposition: inline List-Id: 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: guix-devel@gnu.org Hello, python 3 does not ship a python binary any more, just a binary called python3. That could be useful, since it would allow to install python 2 and 3 side by side. However, all packages relying on a shebang substitution with a python binary now fail. I see two general possibilities to solve the problem: - The simplest one, add a symlink python->python3 in the python 3 package. But then we lose the possibility of installing python 2 and 3 at the same time. Which maybe does not matter? It would only be a problem for a user wanting to install both in the user profile, while all other packages would internally have rewritten their calls to either of the two python versions - In the patch-shebang phase, we could, if the python binary is not available, look for the python 3 binary. But that would mean special code only for python. Personally, I would tend to the first solution. But what do you think? Andreas