[Stackless] Cannot Come!

[Christian Tismer]

Andrew Francis wrote:
> Hello Christian, Andrew, and David:
> 
> --- Andrew Dalke <dalke at dalkescientific.com> wrote:
> 
>> 87. Stackless Python 101
> 
>> I can help with this, and in collaboration with
>> Andrew Francis  perhaps.  I don't have much time to
>> prepare between now and then, so  it would have to be
>>from almost complete notes.  Christian?  What's  
>> the state of that?
> 
> We effectively have a week to work. I have time
> pressure too but I will try my best to help.
> 
> Christian, if you have an outline, perhaps you can
> submit it to me. I have also read the Dalke talk.

Stick with Andrew's talk. It is good.

> Enclosed is a detailed outline of my Stackless/Twisted
> paper.  This is the basis of both the paper and the
> talk. It has a very tutorial, moderately graphic and
> code example structure (my reviewers stated they
> thought Stackless and Twisted needed more of these).
> 
> What I can do is start making my slides immediately so
> that is out of the way. If a Stackless 101 needs
> slides and code, that can be started early. Perhaps I
> can delay the paper (I know it is late). 

I think the 101 talk can be done without preparing
extra slides. Maybe a bit is needed towards your intended
Twisted theme, but this is up to you.

>> 88. Stackless PyPy
> 
> Well I am just starting to look at PyPy. So I can't
> give that talk. However I do refer to PyPy in my
> paper. If I can find the time on the weekend, perhaps
> I can even try out examples in PyPy and see if I can
> incorporate it.

I don't think this makes sense. What I'm saying is
mostly my point of view about PyPy and how it influences
Stackless' future, also about new concepts for stackless.
I would say that this part is very dependant from me.

Although I appreciate the idea very much, I believe
this should be replaced by something else, with a different
topic.

>     9.0 Conclusion
> 
>    1. There is temendious interest in co-routines especially for
>       activities that want an "actor" approach
>    2. Stackless/Twisted compliment each other. Stackless needs Twisted.
>       Stackless can be used to simplify Twisted

I don't believe in "Stackless needs Twisted". It can use it, but
there might be other (simpler?) solutions. But that's not my talk :-)

>    3. The combination can be used to succinctly solve problems that are
>       difficult to solve in another language
>    4. A knowledge of what is happening under the hood
>    5. This knowledge can be used to improve the system and perhaps
>       provide insights into what co-routine technology should look like
>    6. This is a job for PyPy

The sentence under 6. needs some explaining. What exactly is a job
for PyPy?

ciao - chris

-- 
Christian Tismer             :^)   <mailto:tismer at stackless.com>
tismerysoft GmbH             :     Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9A     :    *Starship* http://starship.python.net/
14109 Berlin                 :     PGP key -> http://wwwkeys.pgp.net/
work +49 30 802 86 56  mobile +49 173 24 18 776  fax +49 30 80 90 57 05
PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
       whom do you want to sponsor today?   http://www.stackless.com/