[pypy-dev] OSCON paper
arigo at tunes.org
Sun Jul 6 17:47:43 CEST 2003
On Sun, Jul 06, 2003 at 05:13:02PM +0200, Laura Creighton wrote:
> let me know. Otherwise I am going to select some: if you are going to
> present a paper from a team, it helps to show pictures so people get to'
> know who the team is beyond a long list of names on the Paper.
I found on-line a photo that somebody took of the PyPy sprinters (at the end
of my talk when I awkwardly asked for people to group in front).
> I would also like to use Armin's slide of:
> <WHY> <HOW> <HOW SLOW>
I will do that.
> I also think that the dis example is rather instructive, but I can't
> remember exactly what you ran.
python pypy/interpreter/py.py -S goals/dis-pregoal.py
> I think that, as a presentation, it
> would work to first run a CPython version, and then start the PyPy version.
> Then start to answer questions from the audience about PyPy and wait for
> the expected cheer when we start to get output. What do you think?
It depends on the speed of your machine. At EuroPython I didn't have that nice
2GHz machine that starts printing stuff after "only" 5 to 10 seconds.
> Also is there any code which you would like to be shown? It is
> difficult now for me to see PyPy with fresh eyes, so it is hard for
> me to see where I should begin to explain PyPy code wise.
Maybe: opcode.py, with its nice forest of little functions, for each of the
opcodes, should look weirdly familiar to the big switch in ceval.c for people
who know it; and also an example of the forest of little functions in
objspace.std.xxxobject.py, for example listobject.py, to implement all the
operations on an object.
More information about the Pypy-dev