Callable hooks that iterate through vs hooks that halt

[Christopher Allan Webber]

We can handle notification and transform via the "callable hooks" system, but we don't have a "handler" that is the last one to get it and then things stop.

One way to handle this: have a series of method calling handlers that do things in different ways, like:

• callable_hook_runone: runs them all till they stop
  • which order? Does the last or the first get to claim it?
• callable_hook_runall: runs every one of the hooks
  • likewise... which order?

.. both of those would expect *args, **kwargs and pass those keyword
arguments onto the hooks.

It might also be possible to make some callable classes like this, like:

   callable_hook = CallableHookRunone(
      'some_hookname', accrue=True)  # accrues the results into a list
   results = callable_hook(arg1, arg2, kwarg="foo")

[Christopher Allan Webber]

Just hit master! With tests!

[Christopher Allan Webber]

I'm reopening this, given the new plans I wrote to the list:

• ​http://lists.mediagoblin.org/pipermail/devel/2013-April/000497.html
• ​http://lists.mediagoblin.org/pipermail/devel/2013-April/000498.html

So I'm going to do that then close this out :)