[pypy-dev] Global executable naming policy

Maciej Fijalkowski fijall at gmail.com
Fri Feb 17 09:46:52 CET 2012

On Fri, Feb 17, 2012 at 10:43 AM, Dirkjan Ochtman <dirkjan at ochtman.nl> wrote:
> On Fri, Feb 17, 2012 at 03:41, Aaron DeVore <aaron.devore at 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>)


More information about the pypy-dev mailing list