Re:The first stable release of PyPy3
by ngoldbaum on Friday June 20, 2014 @06:45PM
(#7923323)
It makes sense to use pypy if you're writing pure python code. The second you need a C extension, you're pretty much out of luck. This kills a lot of the appeal for people in the scientific/analytics side of things, who make heavy use of legacy C and Fortran routines.
[ Parent
| on HN ]
Re:The first stable release of PyPy3
by dragonwriter on Friday June 20, 2014 @07:11PM
(#7923418)
> The second you need a C extension, you're pretty much out of luck.
In theory, shouldn't CFFI be the foundation of the solution to that problem?
In practice it works pretty well. I am nearing completion of a rewrite of X's XCB-based python bindings in cffi, and it has worked out quite nicely.
Re:The first stable release of PyPy3
by rguillebert on Friday June 20, 2014 @07:17PM
(#7923437)
yes
Re:The first stable release of PyPy3
by rguillebert on Friday June 20, 2014 @06:55PM
(#7923371)
You can use these C and Fortran routines on PyPy, just not with the CPython C extension API.
There's a lot of established code built around the C API. It's not like it can just be rewritten using CFFI over a weekend.
Re:The first stable release of PyPy3
by rguillebert on Friday June 20, 2014 @08:31PM
(#7923636)
Well, I'm not talking about every C extension in the world, I'm talking about thin bindings around C routines which is what numpy has for fft for example, someone wrote a basic equivalent for numpypy in a few hours with no prior numpypy/cffi knowledge.
Unfortunately, NumPy uses deep knowledge of the CPython API in quite a few places, which is one of the reasons implementing NumPyPy has been so challenging.
Re:The first stable release of PyPy3
by rguillebert on Friday June 20, 2014 @11:58PM
(#7924125)
Another approach should be used for those, but to be clear I wasn't talking about the entire numpy library, I'm talking about things like numpy.fft