[pypy-dev] Questions on the pypy+numpy project
fijall at gmail.com
Thu Oct 20 12:41:11 CEST 2011
On Thu, Oct 20, 2011 at 12:33 PM, Ian Ozsvald <ian at ianozsvald.com> wrote:
>> I was one of the people who responded to that poll, and I have to say that I fall into the category "they actually meant 'SciPy'…".
> I'll note with regards to the survey that I also recall saying Yes to
> numpy but never thinking to explain that I used SciPy, the SciKits and
> Cython for a lot of my work (not all of it but definitely for chunks
> of it). Maybe a second more focused survey would be useful?
I think Armin made it clear enough but apparently not. We're not
against scipy and we will try our best at supporting it. However it's
not in the first part of the proposal - let's be reasonable, pypy is
not magic, we can't make everything happen at the same time.
We believe that emulating CPython C API is a lot of pain and numpy
does not adhere to it anyway. We also see how cython is not the
central part of numpy right now and it's unclear whether cython
bindings would every be done as the basis of numpy array. How would
you do that anyway?
So providing a basic, working and preferably fast array type is an
absolute necessity to go forward. We don't want to plan upfront what
then. We also think providing the array type *has* to break backwards
compatibility or it'll be a major pain to implement, simply because
CPython is too different. And, as a value added, fast operations on
low-level data *in python* while not a priority for a lot of scipy
people is a priority for a lot of pypy people - it's just very useful.
If you have a plan how to go forward *and* immediately get scipy,
please speak up, I don't.
> Ian Ozsvald (A.I. researcher)
> ian at IanOzsvald.com
> pypy-dev mailing list
> pypy-dev at python.org
More information about the pypy-dev