then init the IrcBot class in your main
jus remove this:
to line 68
: doesn't work
but on_command is the main cmd loop
sorry
it's getting annoying
how do I get arguments from a command?
say i have kick <user> <channel>
how do i get user and channel
As for getting arguments from a command, I’m not sure what you’re after. Are you trying as the client (bot) to kick another user from a channel? For that, there’s a
kick method on the ServerConnection (https://github.com/jaraco/irc/blob/master/irc/client.py#L803).
Or if you’re looking to respond to an event where your bot has been kicked, you probably need to define an
on_kick method and it accepts a connection and event argument, with more details in the event that the server supplied. I’m not sure the protocol works that way, but if the server issues a KICK command, you would handle that with on_kick in the client.
I am subclassing SingleServerIRCBot for a simple IRC bot, i was wondering what is best practice for asynchronously doing work and then calling back to my SingleServerIRCBot instance to send a message to the channel
should i just spawn a new thread from the init and pass it a callback function defined within my subclass ?
@zylinx In general, you shouldn’t need to use threads. The
irc.client.Reactor is the default event loop, and it works synchronously (the process_forever method). It has a scheduler instance to which you may add scheduled functions. So you can schedule work to be done. But it really depends on what work it is you want to do. In most cases, the work you need to do is in response to an event from the IRC server and can be handled synchronously. See pmxbot for a mature implementation of a bot built on irc.
One plugin for that bot, the http API at jaraco.pmxbot, does some tricks to run a web server alongside the IRC client to proxy messages. It does that by creating a queue and having the web service run in one thread and periodically poll that queue from the IRC client’s main thread.
@zylinx: Nice work. I realize now that when I jaraco/irc@6dc684d, it made it less clear how one goes about scheduling something. If you’re interested, I’d welcome updates to the docstrings in
irc.client or in the README to enhance the documentation around using the scheduler.
Consider turning on debug logging to see what’s happening in the traffic. Something like
logging.basicConfig(level=logging.DEBUG).
?
You can do SSL by using a custom connection factory. https://python-irc.readthedocs.io/en/latest/irc.html#module-irc.connection
If you want to perform TLS, upgrading the connection within the IRC protocol, that’s not something the library supports, but I’d be open to contributions adding that feature.