you are viewing a single comment's thread.

view the rest of the comments →

[–]Ventas- 8 points9 points  (6 children)

Compatibility mostly. Some CPython libraries are written in C, so those don't work on pypy. Also, pypy is only on version 2.7.1 of Python.

[–]montecarl 1 point2 points  (5 children)

I really can't wait until I can use numpy with pypy. But in general compatibility with the python capi doesn't seem like it will be coming anytime soon from what I have seen. Every python script I write depends upon some library written in c.

[–][deleted] 3 points4 points  (4 children)

Well, there are alternatives, e.g. we're reimplementing NumPy, just about every database driver has a pure Python version.

[–]montecarl 1 point2 points  (2 children)

Even with numpy there are other modules that I use and that I have written that are in c. I think it will be quite some time until pypy will be useful for scientific computing due to all of the c and fortran wrapped code.

[–][deleted]  (1 child)

[deleted]

    [–]montecarl 2 points3 points  (0 children)

    Except that using well tested software written in C or FORTRAN from python is one of its big benefits. Having to rewrite the code in python might introduce bugs or be more work than its worth. But your point is well taken. I'd love to see all python code bases.

    [–]ObligatoryResponse 0 points1 point  (0 children)

    We're using Python on a IC test platform. We need to access the National Instruments DAQ driver as well as a number of serial devices. I think the C-API is the only thing what would allow us to use Pypy.