[pypy-dev] Why `pypy-c.exe`?
ram at rachum.com
Thu Oct 6 15:35:49 CEST 2011
On Thu, Oct 6, 2011 at 3:25 PM, Benjamin Peterson <benjamin at python.org>wrote:
> 2011/10/6 Ram Rachum <ram at rachum.com>:
> > On Thu, Oct 6, 2011 at 3:16 PM, Benjamin Peterson <benjamin at python.org>
> > wrote:
> >> 2011/10/6 Ram Rachum <ram at rachum.com>:
> >> > Why is PyPy's executable called `pypy-c.exe` on Windows? I just
> >> > mine
> >> > to `pypy.exe`, is that okay?
> >> Because it's generated by the "C" backend.
> >> --
> >> Regards,
> >> Benjamin
> > And is that a good enough reason to call it "pypy-c.exe" and risk
> > users?
> Is it confusing?
I personally find it confusing, yes.
Please remember that what's obvious to you is not necessarily obvious to
Here are a few scenarios that could have been true from my point of view:
- There is a `pypy.exe` file somewhere in the distribution, and it should
call `pypy-c.exe` internally.
- PyPy should always be run as `pypy-c` from Windows. (Why? Who knows.)
- I have made some kind of error in my installation and the `pypy.exe`
file is missing.
So unless there is a good enough reason to call it `pypy-c.exe`, I suggest
future releases will be made with an executable of `pypy.exe`.
> > Also, I hope someone could answer my second question.
> No (And by that I mean it's not harmful.)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pypy-dev