Skip to main content

Python: Using Louie with Twisted

Louie "provides Python programmers with a straightforward way to dispatch signals between objects in a wide variety of contexts. It is based on PyDispatcher, which in turn was based on a highly-rated recipe in the Python Cookbook." Louie is like an event system used in a GUI toolkit. Similarly, you can think of Louie as an internal pubsub system. Twisted is a framework for building asynchronous network servers. Using Louie in your Twisted applications can make your applications a little less "twisted".

When you code a Twisted application, you often put a lot of your logic in custom Factory and Protocol classes. However, if you have one application that has to talk to, say, three different types of servers, and you have a custom Protocol and Factory class for each server (perhaps each server speaks a different network protocol), it can be confusing to have your application logic broken up all over the place. Louie can help with that.

When you are implementing a Protocol class, when you receive a new Twisted event, you can generate a Louie event. In that way, you can have a single application-specific class that responds to events from a wide variety of Twisted Protocol classes. When I used this approach on my Twisted application, the code went from being very "scatter brained" to something more linear. I had a bunch of small functions that each responded to Louie events, and all the functions were in order in the same class. It certainly helped me wrangle control of the complexity of the system.

It may seem strange to translate Twisted events into Louie events, but considering the fact that Louie has support specifically for Twisted and considering the fact that I learned this trick from Drew Pertulla, a Twisted user, I know I'm not the only one using this trick.

I have a couple more tips. First of all, Louie tries really hard to pass only the arguments that your function is looking for. Hence, if your function doesn't accept a sender argument, it won't pass a sender argument. This is really helpful, but it can bite you. The magic tends to break down if your function is wrapped by a decorator or if your function is a closure (i.e. a nested function). In these cases, Louie can't figure out exactly which arguments to pass, and stuff can break. However, it's usually easy to work around situations like this once you figure out what's going on.

I have one other mildly off-topic trick for working with Twisted. Queues and Twisted work really well together. If you have one piece of Twisted code that simply reads from a queue and then does something, then other parts of the Twisted code can put things in the queue in a synchronous manner. It sounds simple, but this one trick really helped me out a few different times.

Last of all, I wanted to mention gevent. Twisted is certainly a mature library with support for a range of protocols, but if you're working with green field code, you might want to take a peek at gevent instead. Aside from having excellent performance, it also lets you write code in a synchronous manner, which is helpful for mere mortals like myself. If you're thinking about using Twisted vs. gevent, check out this talk that the Meebo guys gave at PyCon.

Comments

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p