Patrick K. O'Brien wrote: > Robert Wittams wrote: > >>=== Events === >> >>I discussed this with Adrian on IRC a few times, and we agreed that >>events would be a good way to handle quite a number of the issues we >>face - particularly loose coupling. >> >>I've looked around, and it seems like the smart choice for events is >>pydispatcher. >> >> * small >> * bsd >> * reasonably wide use >> >>I also looked at RuleDispatch, but this is a dependency too far right >>now - it is quite a lot bigger in scope, includes C modules, and while a >>lot of what it does is Ubercool®, YAGNI. >> >>So annoyingly they both call themselves 'dispatch', and I don't really >>want to tromp on peoples existing python installation, so... I'm just >>going to stick pydispatcher in django/dispatch for now. There are no >>eggs/setup tools bits I can see for pydispatch atm, so I don't know how >>we would cooperate with a local copy of pydispatcher. Any ideas let me know. > > > Louie was created to address all of those issues. Louie *is* > pydispatcher, plus eggs, minus the name conflict, plus plugin support, > plus a commitment to enhance it even further for projects that adopt > it. So I would strongly encourage you to use Louie instead of > pydispatcher. You can find it here: > > http://louie.berlios.de/
That sounds a lot better, Patrick. Could you recommend how we should bundle this? One advantage we've had so far is that django has no dependencies, so its easy to get up and running. Is there a sane way that we could include louie with django (a snapshot in the svn?), but not in eggs, so that the egg version will do the setuptools-ly correct thing and download/require it? Robert
