Hi Boria, We are indeed starting to think about more focused research areas in PyPy. For example, along these lines, we will need more work on compiler optimizations and generation of code for various architectures, both either statically or just-in-time. More along the lines of interpreters and virtual machines, we could start investigating new aspects that would be useful to code into the interpreter or the translation process: continuations, persistence (either dumping a whole-process image or something more fine-grained), security (running code in a sandbox), and much more, all of which is hinted at in some documentation on Codespeak. Finally, there is also the idea of supporting other dynamic languages than Python by writing an interpreter for them in PyPy.
As Bea pointed out, we should collect these ideas and make them more precise soon: On Fri, Sep 23, 2005 at 04:28:46PM +0100, Boria Feigin wrote: > > 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. In addition, note that this sprint is not meant to focus exclusively on discussion; it's a coding sprint, and we specifically welcome newcomers. If possible and interesting for you, feel invited :-) That's the best way to grasp the basics of PyPy and discuss. Also feel free to say hello in the #pypy IRC channel (irc.freenode.net) and discuss your interests. A bientot, Armin. _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
