public inbox for gentoo-python@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-python <gentoo-python@lists.gentoo.org>,
	 Gentoo Python Project <python@gentoo.org>
Subject: [gentoo-python] Re: Naming of PyPy and PyPy3 executables
Date: Sun, 18 Aug 2013 18:34:36 -0400	[thread overview]
Message-ID: <CAJ0EP40hgaYstZb9Ti5_dbTctywjypcfP0oAHY9wsEHXmT2x=A@mail.gmail.com> (raw)
In-Reply-To: <20130819002932.34135e75@gentoo.org>

On Sun, Aug 18, 2013 at 6:29 PM, Michał Górny <mgorny@gentoo.org> 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.


  reply	other threads:[~2013-08-18 22:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-18 22:29 [gentoo-python] Naming of PyPy and PyPy3 executables Michał Górny
2013-08-18 22:34 ` Mike Gilbert [this message]
2013-08-19 10:43 ` [gentoo-python] " Marien Zwart
2013-08-19 11:07   ` Michał Górny
2013-08-19 13:04   ` Dirkjan Ochtman
2013-08-20 14:20 ` [gentoo-python] " Arfrever Frehtes Taifersar Arahesis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ0EP40hgaYstZb9Ti5_dbTctywjypcfP0oAHY9wsEHXmT2x=A@mail.gmail.com' \
    --to=floppym@gentoo.org \
    --cc=gentoo-python@lists.gentoo.org \
    --cc=mgorny@gentoo.org \
    --cc=python@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox