That's Kam*a*elia, unless you really are talking about a porn star. :) (googling "kamelia python" was pretty interesting). On 8/18/05, Tommi Virtanen wrote:

Antoine Pitrou wrote:

...

For what it's worth, I started writing a pure Python cooperative threads package, some weeks ago. It's called "softlets" and uses, of course, generators. There is a simple scheduler centered around the notion of "wait objects" - you yield a wait object (e.g. a Queue) and it comes back when the underlying condition is satisfied (e.g. the Queue has something to give to you).

You should look at Kamelia.

_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

-- Twisted | Christopher Armstrong: International Man of Twistery Radix | -- http://radix.twistedmatrix.com | Release Manager, Twisted Project \\\V/// | -- http://twistedmatrix.com |o O| | w----v----w-+

On Aug 17, 2005, at 1:20 PM, Christopher Armstrong wrote:

On 8/18/05, tazzo wrote:

...

Hi all, referring to the news about the implementation of PEP 342 in python CVS:

http://dirtsimple.org/2005/08/pep-342-implementation-now-in-cvs.html

I know that is a great news for asynchronous programming in python and for other aspects but I wonder what will be the future of Twisted, what will change (if something will change) in Twisted when PEP 342 will come? I think that with PEP 342 we could write a more readable code but does it mean rewrite all twisted? What is the opinion of Twisted developers??

Have you seen Deferred Generators, in twisted.internet.defer (deferredGenerator and waitForDeferred are relevant)? I'm planning on either adding support for PEP342-style generators to them, or writing an alternate implementation specifically for PEP342. I'm happy about PEP342, because it means I'll no longer have to install a buggy C extension module (greenlet) to get decent cooperative threading.

This integration is very lightweight and doesn't require any mangling of the guts of Twisted.

I'll just note that I am mostly alone amongst the developers of Twisted who think that this kind of cooperative threading + Deferred integration is a good idea. Glyph, Jp, and Allen Short (as he posted) have all said it's a bad idea to have such magical code. On the other hand, it's definitely not as bad as pre-emptive threading, where you basically can't know where context switches will happen.

I think it's a good idea, so long as you know when to use it. It's particularly useful when doing things that are inherently serial when you don't need the power of arbitrary call graphs hooked up to your asynchronous goodness. -bob

Christopher Armstrong wrote:

Have you seen Deferred Generators, in twisted.internet.defer (deferredGenerator and waitForDeferred are relevant)? I'm planning on either adding support for PEP342-style generators to them, or writing an alternate implementation specifically for PEP342.

Yes I saw it and I use it very often, this is why I made the question. When I write code for a intensive and massive cooperation task, writing code in a synchronous-looking way help to understand what happen.

I'm happy about PEP342, because it means I'll no longer have to install a buggy C extension module (greenlet) to get decent cooperative threading.

This integration is very lightweight and doesn't require any mangling of the guts of Twisted.

:-) -- La presente comunicazione potrebbe contenere informazioni riservate e/o protette da segreto professionale ed e' indirizzata esclusivamente ai destinatari della medesima qui indicati. Se avete ricevuto per errore la presente comunicazione, siete invitati a segnalarcelo, rispondendo a questo stesso indirizzo di e-mail, e a cancellare il presente messaggio dal Vostro sistema. E' strettamente proibito e potrebbe essere fonte di violazione di legge qualsiasi uso, comunicazione, copia o diffusione dei contenuti di questa comunicazione da parte di chi la abbia ricevuta per errore o in violazione degli scopi della presente. Il messaggio e' stato analizzato alla ricerca di virus o contenuti pericolosi ed e' risultato NON infetto.