From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brandon Invergo Subject: Re: Python 3 binaries Date: Mon, 02 Sep 2013 08:24:48 +0200 Message-ID: <877gez91vz.fsf@naga.invergo.net> References: <20130831153018.GA5442@debian> <5222282D.7000801@gmail.com> <20130901092817.GA19604@debian> <87d2osoczg.fsf@gnu.org> <20130901143907.GA23394@debian> <87k3j0igz8.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46050) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VGNZK-0001xC-L8 for guix-devel@gnu.org; Mon, 02 Sep 2013 02:25:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VGNZG-0001Z9-0o for guix-devel@gnu.org; Mon, 02 Sep 2013 02:24:58 -0400 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:54552) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VGNZF-0001Z5-TU for guix-devel@gnu.org; Mon, 02 Sep 2013 02:24:53 -0400 In-Reply-To: <87k3j0igz8.fsf@gnu.org> ("Ludovic =?utf-8?Q?Court=C3=A8s=22'?= =?utf-8?Q?s?= message of "Sun, 01 Sep 2013 19:34:03 +0200") 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: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable ludo@gnu.org (Ludovic Court=C3=A8s) writes: > My understanding was that users (really: Python developers) would expect > to get a =E2=80=98python3=E2=80=99 binary when they install the latest, a= nd a =E2=80=98python=E2=80=99 > binary otherwise. It depends. I've grown used to having python(->python3) and python2 binaries in Parabola/Arch, where it is the policy to always have the latest version as the default. > Then that means we don=E2=80=99t really have to worry, and just document = that > the python-3.x package is an unmodified upstream package, with its > binary is called =E2=80=98python3=E2=80=99. I think that is a fine way to do it. The most important part is internal consistency. It seems that the "unmodified upstream" strategy is the path of least resistance, and it will fit with the expectations of all of the Debian-based users out there.=20=20 As for the shebangs, you may well still have to do some patching for some packages, if they were written in python3 but the shebang is for /usr/bin/python. =2Dbrandon =2D-=20 Brandon Invergo http://brandon.invergo.net --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (GNU/Linux) iQEcBAEBAgAGBQJSJC8yAAoJEARu3ubrerdN5J8H/jn9OE0RPPUE3ZgTsD26I9ZM UEgLbtV9j2BAbsAFO6UFGR8mvMF54hiQjkZTGdWFfwEf7Ej+ZoRBtkNaSER7uien 4ySXjSXLq8TlS6hrHunn1NC4JKw3FE4slXNwntawWgCxkiTVZ/xri8Jbk9zshZE8 UJbsOejk0vLjYB7p2dcODWRgRYVb40hc+P8Q5AIxpHrj9o11de+FdWIrRa5Ru4l+ Q1gyON4jQA5cK9M40lvUdtdGpoz9Ajnnkuf6HNRuUVMJuqo7RcvEK2EDaGFl5MS7 NJ2AwWnWwt+4JAJ0w0ev5SxIPSblEolpgSRfFLwGVjkQX8ZluSGHK0Ibdl+9eqk= =0if+ -----END PGP SIGNATURE----- --=-=-=--