[py-dev] "event" branch and architecture

[tav]

Hey Holger,

> i am currently hammering on the svn/py/branch/event branch [*].
> The main intention is to modify py.test's internal architecture
> towards using events and to base reporting and some internal
> processing on these events.

Whilst Zope's event system is nice in its simplicity, it suffers from
many faults once you go beyond the basic use cases. The easiest one to
explain is race conditions that take place with regards to nested
subscriptions. That is, when calling a subscriber/listener with an
event, if that action adds a new listener... and/or notifies the
Hub... you have a lot of pain to work around.

Now, throw in exceptions into that and *boom*, you have a rather messy
minefield.

Can I recommend using Trellis by any chance?

* http://peak.telecommunity.com/DevCenter/Trellis

It solves a lot of very difficult problems rather elegantly and the
core is just 450 lines of code!! Whilst the documentation is a tad
confusing, it does have a lot of it and some parts are written very
nicely.

-- 
hope-this-helps, tav
founder and ceo, esp metanational llp

plex:espians/tav | tav at espians.com | +44 (0) 7809 569 369