A set of improvements to PyPy's NumPy module, particular goals include: more datatypes, better support for scalar data, multi dimensional data, and improvements to the JIT to remove casts.
Authors
Contributors
Recent Posts
See AllAnnouncing Topaz, an RPython powered Ruby interpreter
Hello everyone Last week, Alex Gaynor announced the first public release of Topaz, a Ruby interpreter written in RPython. This is the culmination of a part-time effort over the past 10 months to provide a Ruby interpreter that implements enough interesting constructs in Ruby to show that the RPython toolchain can produce a Ruby implementation fast enough to beat what is out there. Disclaimer Obviously the implementation is very incomplete currently in terms of available standard library. We are ...
CFFI 0.5
Hi all, A short notice to tell you that CFFI 0.5 was released. This contains a number of small improvements from 0.4, but seems to otherwise be quite stable since a couple of months --- no change since January 10, apart from the usual last-minute fixes for Python 3 and for Windows. Have fun! Armin
NumPyPy 2013 Developer Position
Introduction Proposed herein is a part-time fellowship for developing NumPy in PyPy. The work will initially consist of 100 hours with the possibility of extension, until the funds run out. Development and improvement of PyPy's NumPyPy (as with most Open Source and Free Software) is done as a collaborative process between volunteer, paid, and academic contributors. Due to a successful funding drive but a lack of contributors willing to work directly for PyPy, we find ourselves in the enviable ...
Recent Commits
See Allannmodel: make SomeStringOrUnicode explicitly a pure implementation detail This class exists to avoid duplicating the implem...
annmodel: make SomeStringOrUnicode explicitly a pure implementation detail This class exists to avoid duplicating the implementations of SomeString and SomeUnicodeString, but as far as any user of this module should be concerned those two types are totally unrelated, because in RPython they are unrelated.
annmodel: make SomeStringOrUnicode explicitly a pure implementation detail This class exists to avoid duplicating the implem...
annmodel: make SomeStringOrUnicode explicitly a pure implementation detail This class exists to avoid duplicating the implementations of SomeString and SomeUnicodeString, but as far as any user of this module should be concerned those two types are totally unrelated, because in RPython they are unrelated.
signatures: cut basestring, not a valid annotation
signatures: cut basestring, not a valid annotation
signatures: cut basestring, not a valid annotation
signatures: cut basestring, not a valid annotation
signatures: cut basestring, not a valid annotation
signatures: cut basestring, not a valid annotation

