Thanks for the quick reply. > >Can anyone suggest pointers to areas of PyPy that need work? Or, better > >yet, ideas that need further development -- research in literature, > >prototyping, and implementation? > > I will try to answer this - maybe the others can fill in? > > First of all - thank you for your interest in PyPy! We have lots of work Great!
> ;-) - the main question is how familiar you are with Python specifically Reasonably familiar (a couple of university projects, about 3.5K lines in total), though there's definitely room to improve :) > and wether you have read the documentation that exists on Codespeak? Not yet. I'll do it this weekend. > As to the research aspect - we are just now entering our second phase of > the funded (EU) side of PyPy and the upcoming 9 months is all about > optimizations and exploration so there should be interesting stuff to do > that could fit well for a final year project. :) > In October, 10-16th to be more exact we will meet up to sprint in Paris > and we will devote some time to plan the work in phase 2 in some more > detail. Maybe we could get back to you after that? > > Meanwhile (if you havent done so already) you could read some of the > documentation and identify areas of interest to you? Sounds good. I'll read the docs, subscribe to the list, and send another e-mail about 15th or 16th of October. > >Thanks for your time. > > > >Please CC me -- I am not on the list. > > > >-- > >Boris > > Cheers > > Beatrice Düring > Assistant project manager/PyPy > The non techie person ;-) -- Boris _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
