[pypy-dev] v5.3.0 numpy support (specifically numpy/core/src/multiarray/multiarray.c.src)

[Matti Picus]

No, the latest release does not solve this issue. And in a bit more detail:

The latest release supports upstream numpy (mostly) using a C-API 
compatibility layer we call cpyext. This is a totally different approach 
than using our internal _numpypy module and the python-level code from 
bitbucket/pypy/numpy.

While the new approach allows you to use upstream (i.e. 
github.com/numpy/numpy) numpy over the latest release of PyPY, the code 
will run much slower, and the JIT will not be able to help since it 
cannot look inside C code. We have some ideas on how to make this fast, 
but they are just ideas right now.

Matti

On 09/06/16 00:39, Eli Stevens (Gmail) wrote:
> I asked about the following about a month ago:
>
> ======================================================================
> ERROR: Failure: ImportError (No module named numpy.core.multiarray_tests)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>    File "/home/elis/venv/ppdb/site-packages/nose/loader.py", line 418,
> in loadTestsFromName
>      addr.filename, addr.module)
>    File "/home/elis/venv/ppdb/site-packages/nose/importer.py", line 47,
> in importFromPath
>      return self.importFromDir(dir_path, fqname)
>    File "/home/elis/venv/ppdb/site-packages/nose/importer.py", line 94,
> in importFromDir
>      mod = load_module(part_fqname, fh, filename, desc)
>    File "/home/elis/venv/ppdb/site-packages/numpy/core/tests/test_multiarray.py",
> line 22, in <module>
>      from numpy.core.multiarray_tests import (
> ImportError: No module named numpy.core.multiarray_tests
>
> And was told by Matti:
>
>> multiarray_tests comes from numpy/core/src/multiarray/multiarray.c.src which is compiled to a C-API module.
>> We skip building it as we have quite a way to go before we can support that level of C-API compatibility.
> Is there any change in behavior expected with the new release
> regarding these kinds of errors?
>
> Thanks,
> Eli
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> https://mail.python.org/mailman/listinfo/pypy-dev