As far as numpy, the last few blog status posts are probably give the best idea:
http://morepypy.blogspot.com/2014/04/numpy-on-pypy-status-update.html http://morepypy.blogspot.com/2014/03/numpy-status-update-february.html Somewhere in there I mention count of tests passing out of tests total -- that's probably the best, albeit approximate indicator of functionality. You could pull an updated count from the nightly tests: http://buildbot.pypy.org/builders/numpy-compatability-linux-x86-64 On Tue, May 20, 2014 at 4:56 PM, Antonio Cuni <anto.c...@gmail.com> wrote: > Hi all, > > I am preparing the usual "PyPy status talk" which I'll give to the > upcoming Pycon Italy, which is going to cover what happened in the last two > years of PyPy. > > If you are interested, the draft slides are here: > > https://bitbucket.org/pypy/extradoc/src/tip/talk/pycon-italy-2014/talk.rst?at=extradoc > > In the talk, I will to give an overview of the current status of the > various subprojects, so I'd be glad if you could help because you surely > know better than me the status of the area of your competence :) > > David: what is the current status of PyPy on ARM? Should I say "it just > works" or there is something more to add? What about performance? > > Matti, Brian: what about numpy? Since people like numbers, what percentage > of numpy we can consider completed? > > Philip: same question for py3k. Is it still considered beta quality or we > can say it's stable? > > Alex, Maciej: I'll also briefly talk about other frontends, so Topaz and > Hippy. How much complete are they? What are the performance? I know that > hippy is still actively developed, but what about Topaz? > > Other than what I asked, I'll also highlight CFFI and STM. If anyone has > ideas for other cool things which happened in PyPy since 2012, suggestions > are welcome :) > > thank you very much! > Anto >
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
