[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pypy-dev
Subject:    Re: [pypy-dev] Global executable naming policy
From:       Maciej Fijalkowski <fijall () gmail ! com>
Date:       2012-02-17 8:46:52
Message-ID: CAK5idxT1LY-sh2z2upgQBGfPVaecQ0qsB3wGDOK7a909-Kc0NQ () mail ! gmail ! com
[Download RAW message or body]

On Fri, Feb 17, 2012 at 10:43 AM, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
> On Fri, Feb 17, 2012 at 03:41, Aaron DeVore <aaron.devore@gmail.com> wrote:
>> There currently isn't an official naming scheme for the PyPy
>> executable for system installations. Of the 3 setups I've seen, the
>> official build uses pypy, Arch Linux uses pypy, and Gentoo Linux uses
>> pypy-c<version>.
>
> FWIW, if people feel it should be pypy instead of pypy-c, I'm happy to
> change it.

We (arbitrarily) decided pypy for binary distributions. It's still
called pypy-c when it is compiled. I would go for pypy.

Note that there is no point in pypy2.7-1.9, since there will never be
any other pypy2 but pypy2.7.

pypy3.3-1.9 sounds relatively obscure and verbose to me, but whatever.
How about pypypy for pypy3 instead? (<joke>)

Cheers,
fijal
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
[prev in list] [next in list] [prev in thread] [next in thread]