3 ms·

I was looking at the example code, where bot logic and the run() was defined in the same module. That can't be reloaded. The reloader looks like it works for "

I was looking at the example code, where bot logic and the run() was defined in the same module. That can't be reloaded. The reloader looks like it works for "plugins." It all seems unnecessarily complex to me. Also, your handlers should be provided with the channel in which the command was triggered. That doesn't seem to be set in the context dict that is passed to commands. Another thing is that the bot model is very restrictive, as I've often seen with this sort of tool: You have events and commands, and that's it. It looks like the case of "try and match this regex, and do something with the result" would be possible, but made overly complex.

llambda 15y ago
I'm not sure what you mean when you say it can't be reloaded. In fact the only part of the code that cannot be hot-loaded is the socket connection (although this can be achieved if done properly) but because everything is decoupled, it's simple to reload even the framework itself, on the fly. And of course, the application written with the framework is wholly reloadable. This works just as Flask does and is in fact modeled after it. Edit: I'm not sure why you think it would be restrictive, the entire line is available, it's conveniently parsed, and you're free to attach plugins to commands and hooks (what else do you want to attach them to, that's pretty much the extent of what happens with IRC). Regex? No problem: attach a function to an IRC command (this is the event decorator) and check the line for your patterns (context.line). If it seems too complicated to you or for your application, that's fine, as I said, this was a project I did for my own edification.