hello pypy-dev, the sprint is over. It was a pretty intensive and what we think successful week. It proved to be impossible to do daily reports or communicate much with the outside world, sorry. It was hard enough to keep up with what everybody was doing. Watching Twin Peaks in the night didn't help much, either :^) The most interesting result is a somewhat running interactive pypy interpreter which is pretty satisfying. It turned out that the "objectspace" design makes a great lot of sense. The concept of dispatching operations on objects to a "library" is already in CPython but PyPy makes this very explicit. There also is an explicit distinction between interpreter-level and application level objects. Whereever possible we work in good old python application space. The interpreter runs with "normal" python, too, but it is even more more explicit in its code and naming. The PyPy-Interpreter only runs on the "trivial" objectspace (dispatching directly to CPython) but we had good progress on doing a "std" objectspace that reimplements all the CPython Types in Python. The "intobject.py" is pretty complete and gives a good example of a conversion from C-Python to Py-Python. When the StdObjSpace is more complete we are eager to generate all kinds of code from it. The first target may be regenerating a python interpreter/core in C-CPython. Those of you familiar with the ceval.c and friends will recognize strong similarities with CPython in http://codespeak.net:8080/svn/pypy/trunk/src/pypy/interpreter/pyframe.py Best of all, we did'nt have big naming, license, PEP308 or coding-style discussions. It's pypy, MIT-license, drop it and http://codespeak.net:8080/svn/pypy/trunk/doc/coding-style.txt This coding-style document was agreed on in much less than one hour which must be a world record, i guess :-) Also we now have "subversion" serving almost all documents and configurations of our project (including the website). We got the server python svn-bindings running so we can directly script all layers of subversion in the future. We refactored parts of our Wiki-code (MoinMoin-based) to have its pages also subversion controled. Although it's not complete you can already edit wiki-pages locally on your machine. I expect website updates to have to wait a bit, though, as most of the sprinters need to catch up with their other activities and slow down a bit. While it is impossible to post a summary of the discussions i guess that these discussions will influence the future development of pypy quite a bit and reflect to the pypy-dev list, of course. Last but not least, we (kind of) fixed another sprint between 20th and 24th of June 2003 right before EuroPython (which is between 25th to 27th). We may do an in-between sprint at beginning of May in Sweden. so much for my little report, have fun, holger
participants (1)
-
holger krekel