<i>"We would like to thank our donors for the continued support of the PyPy project, and for those who donate to our three sub-projects, as well as our volunteers and contributors (10 new commiters joined PyPy since the last release). We’ve shown quite a bit of progress, but we’re slowly running out of funds. Please consider donating more, or even better convince your employer to donate, so we can finish those projects! The three sub-projects are:
"</i><p>PyPy are doing such incredible work and they seem to ask for very little in the way of funding to make it happen (and they're very explicit about where they're going to spend the money).<p>Why is it that there aren't more donations from the industry? Is it just a marketing issue? Do they need to do a snazzy kickstarter video to build the hype?
Congrats to the PyPy team on what sounds like a pretty big release!<p>Something in the release notes caught my eye:<p>> The past months have seen pypy mature and grow, as rpython becomes the goto solution for writing fast dynamic language interpreters.<p>I asked this question[1] on the Perl 6 thread from a few days ago but didn't get an answer. Does anyone know why on earth the Perl 6 folks created yet another dynamic language VM+JIT with MoarVM instead of taking advantage of all the great work done with PyPy? Does anyone know whether PyPy was even considered as a target before writing MoarVM?<p>[1] <a href="https://news.ycombinator.com/item?id=8982229" rel="nofollow">https://news.ycombinator.com/item?id=8982229</a>
I'm really looking forward to the numpy specific announcements. Numpy is THE basic building for every single scientific library - if pypy can get a high performance numpy, that will go a long way towards allowing scientific users to use pypy (there is still the detail of libraries that use the c-api to wrap c libraries, but cffi is pretty neat).
Assuming trunk and 2.5.0 are roughly the same thing it seems like a decent performance increase <a href="http://speed.pypy.org/" rel="nofollow">http://speed.pypy.org/</a>
FYI, you'll still need to compile a specific gevent branch if you want to use it with this. lxml built fine, uWSGI seems OK too (except for the lack of gevent workers in my build).<p>Things seem adequately speedy, haven't investigated the network throughput tweaks yet.