Trellis was forked by Sergey Schetinin a few weeks ago because Philip J Eby has not been doing anything with Trellis recently (I believe his last email to the PEAK mailing list before talk about forking came up, was back in January). It basically aims to be a maintained version of Trellis. The main interest in Trellis seems to be in using it for GUI, networking and ORM and this seems to be Sergeys focus. I have not looked at what it supports in regards to networking or what is planned, but from my (very limited) use of Trellis in the past, I imagine it would be a great way to code networked applications. If anyone does take a look at this, I'd love to hear about it.
2009/7/7 <[email protected]>: > > Its looks weird, yet wonderful, I shall be examining it further, thank you. > >> No idea if this is useful but this just poped up in my RSS reader from >> PyPI: >> >> Trellis-fork 0.1-dev-r70 >> from PyPI recent updates >> Fork of Trellis: "A simple 'untwisted' approach to event-driven >> programming" >> >> Remember hearing something about Trellis a while back but never looked in >> it. >> >> Other Michael >> >> 2009/7/7 Michael Twomey <[email protected]> >> >>> >>> On Tue, Jul 7, 2009 at 12:36, <[email protected]> wrote: >>> > >>> > Anyone know of a good list? >>> > >>> >>> > I'm trying to get an overview of whats out there, so far I have >>> > >>> > Twisted >>> >>> - Good but it's twisted so the usual deferred vs not deferred argument >>> can ensue amongst folks. Obviously well tested and proven. >>> >>> > asyncore >>> >>> - I believe most folks don't recommend this, choosing twisted instead. >>> It's main advantage is it's bundled with python but I know some folks >>> have some very unkind words to say about it. >>> >>> > Medusa >>> >>> - Ditto(ish) >>> >>> > Kamaelia (not sure if this is actually async, have to look it over) >>> >>> This one is quite interesting, uses inbox/outbox approach, similar to >>> erlang in some ways. Wire up your component's inboxes and bob's your >>> uncle. I'd recommend looking at this one, Michael Sparks and co have >>> put a lot of work into it. AFAIK it implements the actor model. >>> >>> > Eventlet >>> > >>> >>> This one pops in and out discussions, depending on how much >>> maintenance it's getting at any given moment. I really don't know how >>> much wide spread use it gets (it's the one second life settled on >>> isn't it?) >>> >>> > Is there anything interesting out there I'm missing? >>> > >>> >>> If you are on the market I strongly recommend stackless and any >>> framework based on that. Again it can implement the actor model, plus >>> eve proves it works in industrial grade environments. >>> >>> I believe concurrence is layered on top of this. >>> >>> mick >>> >>> > >>> >> >> >> -- >> Michael Kerrin - 087 6883894 >> >> > >> > > > > > > -- Daniel Kersten. Leveraging dynamic paradigms since the synergies of 1985. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Python Ireland" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.ie/group/pythonireland?hl=en -~----------~----~----~----~------~----~------~--~---
