hello again. To start the gsoc ideas list off...
- port jit to 64 bit (maybe too short for 3 month project, if so start on ARM after amd64?). - speed up ctypes wrapper. - GIL removal work. - python2.6/2.7/py3k features. - ctypes bindings for database adaptors (would be good for ironpython, jython, and even cpython too). - faster ctypes module. (by using jit?) - cpython bridge module. Either load pypy as cpython extension or the otherway around. To allow gradual porting. - ironclad port to pypy. To allow loading cpython C extensions. eg, ironpython can run numpy with this. - revive javascript/flex backend. - improvements to java/.net backend. - AOT compilation research - to allow compiling to iphone for example. I guess this list could also be put on a page looking for sponsors? To give sponsors something concrete they can pay a contract for. eg, 'approximately 2-3 months work(24,000 euros) to get X benefit, as well as a logo+link on our sponsors page... etc.' Anyway... those are some of the areas I can think of from past discussions. I'm sure pypy project members have a better idea of what would be good for gsoc students to work on? cu, On Tue, Mar 2, 2010 at 3:51 PM, René Dudfield <[email protected]> wrote: > hi, > > gsoc is on again... for your information the python mailing list for it is > here: > http://mail.python.org/mailman/listinfo/soc2010-mentors > > It would be good to have a wiki page(or blog post? ... err a text file > available via http) of project ideas for pypy... if there are any pypy > people mentoring that is. With the pygame project last year, we found > having a project page for suggestions of acceptable projects helped students > pick things they were interested in, and things the project would be happy > with. > > > > cu >
_______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
