Stackless Python, eventual merge?

[Christian Tismer]

Martin v. Loewis wrote:
> Christian Tismer <tismer at tismer.com> writes:
> 
> 
>>>Academically, I don't think the results are unpredictable, as
>>>micro-thread switch occur at predictable points in processing.
>>
>>Yes, right now, but this will change pretty soon.
> 
> 
> You mean, tasklet switches will occur at unpredictable times?
> 
> This sounds like a bad idea.

Old Stackless had pre-emptive scheduling, and everybody
was happy with it. Microthreads were the major application.
I need to support this again, but in a much more fine-grained
implementation.
It is (again) the user's decision whether he allows
free scheduling of certain code. Some people love it,
some people hate it. I don't care, but support it all.

...

>>I have to do rigid locking of every unknown piece of code, until
>>somebody explicitly claims some code to be switchable.
> 
> 
> This, again, sounds terrible. I doubt it will help, and users will
> complain.

I don't think it makes sense to continue this
discussion in a public forum. Let's sit together
with a beer at some time, and you will see what
I have in mind. I'm not aiming at complaining
users. Instead, they will get the same safe default
behavior as with the old version, only better.
My fault is to provide a flare gun without a locking
bolt. Will to whatever it needs to fix this.

ciao - chris
-- 
Christian Tismer             :^)   <mailto:tismer at tismer.com>
Mission Impossible 5oftware  :     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 89 09 53 34  home +49 30 802 86 56  pager +49 173 24 18 776
PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
      whom do you want to sponsor today?   http://www.stackless.com/