From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 5FE461381F3 for ; Sun, 18 Aug 2013 22:34:46 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3D6A1E0AE7; Sun, 18 Aug 2013 22:34:41 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BF02FE0AE7 for ; Sun, 18 Aug 2013 22:34:40 +0000 (UTC) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id B4C4D33EB88 for ; Sun, 18 Aug 2013 22:34:39 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id hi8so2568627wib.1 for ; Sun, 18 Aug 2013 15:34:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=+VJoi/QvhPTkOaEHjGMtdERXg3pCeBefy7PM/jWGrnE=; b=UZcvd4c/PwJuAQhhUH9lgGURmo5aDyMhkSQ6ZjWpX5abXynCeFI1RX+D6PtJuGIeEv 4Xi80n0mhctV2aCC8uq5ZAKoXwmzyu7AveUXnLor66m/8+lLBy6u1GkyE2gOQogtsJPd OH24MvYAwYiLZy58vX+B8gjFBHF15bhuzpmiDLH5nYLxLoY+ukG+TQ4wFW++0YjhODVK ICd1f9gSwFluO3wVM7xFMEL++SlA29VJSTp4FEedC0o5Ze001QkBKfbqrgF5WpFEVOv8 roSqN23pnvp5Kv9jSRYbWbzIzULlnvF1NaQiW/d6OcielsqxpBoEJ9uDp3dhakb2GyIS i8aA== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Discussions centering around the Python ecosystem in Gentoo Linux X-BeenThere: gentoo-python@gentoo.org X-BeenThere: gentoo-python@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.180.100.225 with SMTP id fb1mr5847765wib.22.1376865276968; Sun, 18 Aug 2013 15:34:36 -0700 (PDT) Received: by 10.194.39.231 with HTTP; Sun, 18 Aug 2013 15:34:36 -0700 (PDT) In-Reply-To: <20130819002932.34135e75@gentoo.org> References: <20130819002932.34135e75@gentoo.org> Date: Sun, 18 Aug 2013 18:34:36 -0400 Message-ID: Subject: [gentoo-python] Re: Naming of PyPy and PyPy3 executables From: Mike Gilbert To: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= Cc: gentoo-python , Gentoo Python Project Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 34b6a44d-7aaf-4e4a-8809-294a6b01a595 X-Archives-Hash: baf54057d99440a5ae5d471596e52907 On Sun, Aug 18, 2013 at 6:29 PM, Micha=C5=82 G=C3=B3rny = wrote: > Hello, > > Let's open an official discussion about this. > > > First of all, what happens on Gentoo. The PyPy's build process creates > an executable named 'pypy-c'. We install it with this name, and symlink > as /usr/bin/pypy-cX.Y for each PyPy version. We don't do any 'common' > wrapper for PyPy. > > Upstream's packaging scripts, however, rename the 'pypy-c' executable > to 'pypy'. All other distros I have checked (Arch, Debian, Fedora, > Ubuntu) install a single /usr/bin/pypy for them. They don't support > multiple versions though. > > At the point, it seems reasonable to drop our '-c' addition and just > use 'pypyX.Y' (+ 'pypy') instead. We could do this starting with 2.1 > but... > > > Since v2.1, PyPy has been 'split' into PyPy and PyPy3, the former being > Python2 variant and the latter Python3. Both share the same versions > (that is, there's PyPy 2.1 and PyPy3 2.1). > > From what floppym checked, the build process builds plain 'pypy-c' > as well. Alike regular PyPy, upstream's scripts rename it to 'pypy'. > > Since PyPy3 is still in beta, only Arch Linux has packages for it. It > installs a single /usr/bin/pypy3 (what a surprise). > > > This raises the question: how should we name our PyPy executables? > While I really like the 'pypyX.Y' idea, I don't really want to see > 'pypy32.1' :). We could go for 'pypy-X.Y' and 'pypy3-X.Y' but that would > be inconsistent with CPython (pythonX.Y) and Jython (jythonX.Y0). > A somehow ugly alternative would be to use 'pypy-cX.Y' and 'pypy3-cX.Y' > but that is quite a custom invention. > > Your thoughts? > How about pypypy2.1? ;-) Sorry, I couldn't resist.