> approach. That sounds the easiest, although I'm still interested in > any idioms or other proven approaches for this sort of thing. > > ~Sean
Idioms certainly have their place, but in the end you want clear, correct code. In the case of multi-threaded programming, synchronization adds complexity, both in code and concepts, so figuring out a clean design that uses message passing tends to be clearer and more robust. Most idioms are just a pattern to which somebody found a simple, robust solution, so if you try to think of a simple, robust solution, you're probably doing it right. Especially in trivial cases like the one above. Justin -- http://mail.python.org/mailman/listinfo/python-list