pytwitcherapi.chat.client
¶
IRC client for interacting with the chat of a channel.
Classes¶
ChatServerStatus (server[, ip, port, status, ...]) |
Useful for comparing the performance of servers. |
IRCClient (session, channel[, queuesize]) |
Simple IRC client which can connect to a single pytwitcherapi.Channel . |
Reactor ([on_connect, on_disconnect]) |
Reactor that can exit the process_forever loop. |
Reactor3 ([on_connect, on_disconnect]) |
Reactor that uses irc v3 connections |
Functions¶
add_serverconnection_methods (cls) |
Add a bunch of methods to an irc.client.SimpleIRCClient to send commands and messages. |
Data¶
absolute_import |
|
log |
Instances of the Logger class represent a single logging channel. |
-
pytwitcherapi.chat.client.
add_serverconnection_methods
(cls)[source]¶ Add a bunch of methods to an
irc.client.SimpleIRCClient
to send commands and messages.Basically it wraps a bunch of methdos from
irc.client.ServerConnection
to beirc.schedule.IScheduler.execute_after()
. That way, you can easily send, even if the IRCClient is running inIRCClient.process_forever
in another thread.On the plus side you can use positional and keyword arguments instead of just positional ones.
Parameters: cls ( irc.client.SimpleIRCClient
) – The class to add the methods do.Returns: None
-
pytwitcherapi.chat.client.
absolute_import
= _Feature((2, 5, 0, 'alpha', 1), (3, 0, 0, 'alpha', 0), 16384)¶
-
pytwitcherapi.chat.client.
log
= <logging.Logger object>[source]¶ Instances of the Logger class represent a single logging channel. A “logging channel” indicates an area of an application. Exactly how an “area” is defined is up to the application developer. Since an application can have any number of areas, logging channels are identified by a unique string. Application areas can be nested (e.g. an area of “input processing” might include sub-areas “read CSV files”, “read XLS files” and “read Gnumeric files”). To cater for this natural nesting, channel names are organized into a namespace hierarchy where levels are separated by periods, much like the Java or Python package namespace. So in the instance given above, channel names might be “input” for the upper level, and “input.csv”, “input.xls” and “input.gnu” for the sub-levels. There is no arbitrary limit to the depth of nesting.