Due to short time, I'll just submit this structure. We can discuss and change it probably further (but 3 slots sounds lik On Wed, May 21, 2008 at 5:06 PM, Maciej Fijalkowski <fijall@gmail.com> wrote:

From a brief discussion with people, I suggest the following:

1. Do an official pypy status talk, which will describe what cool stuff you can do with pypy, where we are, where we're going and what are our goals. (45 minutes incl questions)

2. Afterwards, do an architecture talk (I suggest 30 min including questions), for those who want to dig deeper

3. Do some obscure talk. Rough idea is to give some details about garbage collection strategies and what does it mean for various operations (also 30 min).

We can do the last as BoF or Open Session, but a talk would be nicer I suppose.

I can do first and third, probably with someone.

Cheers, fijal

On Tue, May 20, 2008 at 4:36 PM, Jacob Hallén <jacob@openend.se> wrote:

...

On tisdagen den 20 maj 2008, Beatrice During wrote:

...

Hi there

Thursday 22nd of May is the submission deadline for EuroPython 2008 (http://www.europython.org/FrontPage, 7-12th of July).

Question 1: Are any pypy people going to submit talks?

I have submitted a high level talk about PyPy - essentially the architecture overview I presented on the US tour, plus information about where we stand today.

Jacob _______________________________________________ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev

onsdagen den 21 maj 2008 skrev Maciej Fijalkowski:

Bah, sent in the middle

Due to short time, I'll just submit 2 more talks with this structure (assuming that jacob reserved the "architecture" one). We can discuss and change it probably further (but 3 slots sounds like a reasonable solution anyway).

Cheers, fijal

This is what I have submitted: Title: PyPy for the rest of us - A lightweight introduction for people who want to understand the big picture Target audience: intermediate (concerning Python), novice (concerning PyPy) Theme: Python Language Talk format: 30 minutes Summary: PyPy is a new implementation of Python that has been worked on for about 4 years. It has been usable for a couple of years, but there hasn't been a compelling reason for Python users to use PyPy so far. We expect this to change in the next 6-12 months, so now is the time to find out what PyPy is about, This talk explains the big picture of what PyPy is and isn't, in a way that is accessible to everyone. If you want to understand how a JIT compiler generator works, this talk is not for you. If you want to understand where PyPy stands today and what hurdles remain to make your code go faster, you should attend. Speaker: Jacob Hallén Biography: Jacob has been involved with the PyPy project since its first sprint. He has done a lot of auxilliary work like coding library modules, writing funding proposals and doing project management tasks. This means that he has had to bend his mind around the intricate results of the genius coders that surround him.