On Tue, Oct 18, 2011 at 1:41 PM, Armin Rigo <ar...@tunes.org> wrote: > Hi, > > On Tue, Oct 18, 2011 at 14:19, Stefan Behnel <stefan...@behnel.de> wrote: >> The other situation is where PyPy does its own thing and supports some NumPy >> code that happens to run faster than in CPython, while other code does not >> work at all, with the possibility to replace it in a PyPy specific way. > > I think you are disregarding what 8 years of the PyPy project should > have made obvious. Yes, some code will not run at all on PyPy at > first, and that amount of code is going to be reduced over time. But > what we want is to avoid a community split, so we are never, ever, > going to add and advertise PyPy-only ways to write programs.
Ok. In that case, it is fair to say that you are talking about a full reimplementation of the whole scipy ecosystem, at least as much as pypy itself is a reimplementation of python ? (since none of the existing ecosystem will work without the C numpy API). Sorry for being dense, just want to make sure I am not misrepresenting your approach, David _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
