[10:41:48] <xrogaan_> i had no idea one could do that in python
[10:42:18] <jaraco> decorators are pretty powerful.
[10:42:53] <jaraco> The trick for something like pmxbot is that the decorators register the functions as handlers, which can be looked up in a dictionary of commands.
[10:44:38] <xrogaan_> well, i aim to create a modular ircbot. I don't think it would work that way.
[10:44:49] <xrogaan_> see, every module come with its own set of commands
[10:45:06] <jaraco> If you want to add commands to pmxbot, just create a package according to the pmxbot README, and we can install it.
[10:45:42] <xrogaan_> what happens in case of collision ?
[10:45:53] <jaraco> Currently, first registered wins.
[10:46:08] <jaraco> And registration occurs in order of setuptools entry points.
[10:46:14] <xrogaan_> i'm writting my own thing btw
[10:48:23] <xrogaan_> i was just wondering how you came up with the command listing :p
[10:51:41] <jaraco> oh. I see. The bot just cycles through the registry. https://bitbucket.org/yougov/pmxbot/src/b26c4e81e194/pmxbot/commands.py#cl-791
[10:53:38] <xrogaan_> I'm currently thinking about using a "false" dict to manage modules and related commands
[17:59:10] <iElectric> J1m: what are your plans for buildout 2.x docs?
[18:37:32] <J1m> iElectric, my first choice is for someone else to make the plans. :)
[18:37:44] <J1m> Y'all seem to be off to a good start.
[18:38:53] <J1m> At a high level, I'd like to see a not-to-long introduction on the package page (pypi) that describes the 2 main use cases, and links off to sphinx docs.
[18:39:59] <J1m> My recommendation for the sphinx docs is to have a fairly brief into/getting started page and then 2 high-kevel sections: how-tos and reference docs.