A Python robot that edits Wikipedia and interacts with people over IRC https://en.wikipedia.org/wiki/User:EarwigBot

241 regels
12 KiB

  1. Customizing
  2. ===========
  3. The bot's working directory contains a :file:`commands` subdirectory and a
  4. :file:`tasks` subdirectory. Custom IRC commands can be placed in the former,
  5. whereas custom wiki bot tasks go into the latter. Developing custom modules is
  6. explained in detail in this documentation.
  7. Note that custom commands will override built-in commands and tasks with the
  8. same name.
  9. :py:class:`~earwigbot.bot.Bot` and :py:class:`~earwigbot.bot.BotConfig`
  10. -----------------------------------------------------------------------
  11. :py:class:`earwigbot.bot.Bot` is EarwigBot's main class. You don't have to
  12. instantiate this yourself, but it's good to be familiar with its attributes and
  13. methods, because it is the main way to communicate with other parts of the bot.
  14. A :py:class:`~earwigbot.bot.Bot` object is accessible as an attribute of
  15. commands and tasks (i.e., :py:attr:`self.bot`).
  16. The most useful attributes are:
  17. - :py:attr:`~earwigbot.bot.Bot.config`: an instance of
  18. :py:class:`~earwigbot.config.BotConfig`, for accessing the bot's
  19. configuration data (see below).
  20. - :py:attr:`~earwigbot.bot.Bot.commands`: the bot's
  21. :py:class:`~earwigbot.managers.CommandManager`, which is used internally to
  22. run IRC commands (through
  23. :py:meth:`commands.call() <earwigbot.managers.CommandManager.call>`, which
  24. you shouldn't have to use); you can safely reload all commands with
  25. :py:meth:`commands.load() <earwigbot.managers._ResourceManager.load>`.
  26. - :py:attr:`~earwigbot.bot.Bot.tasks`: the bot's
  27. :py:class:`~earwigbot.managers.TaskManager`, which can be used to start tasks
  28. with :py:meth:`tasks.start(task_name, **kwargs)
  29. <earwigbot.managers.TaskManager.start>`. :py:meth:`tasks.load()
  30. <earwigbot.managers._ResourceManager.load>` can be used to safely reload all
  31. tasks.
  32. - :py:attr:`~earwigbot.bot.Bot.frontend` /
  33. :py:attr:`~earwigbot.bot.Bot.watcher`: instances of
  34. :py:class:`earwigbot.irc.Frontend <earwigbot.irc.frontend.Frontend>` and
  35. :py:class:`earwigbot.irc.Watcher <earwigbot.irc.watcher.Watcher>`,
  36. respectively, which represent the bot's connections to these two servers; you
  37. can, for example, send a message to the frontend with
  38. :py:meth:`frontend.say(chan, msg)
  39. <earwigbot.irc.connection.IRCConnection.say>` (more on communicating with IRC
  40. below).
  41. - :py:attr:`~earwigbot.bot.Bot.wiki`: interface with the
  42. :doc:`Wiki Toolset <toolset>`.
  43. - Finally, :py:meth:`~earwigbot.bot.Bot.restart` (restarts IRC components and
  44. reloads config, commands, and tasks) and :py:meth:`~earwigbot.bot.Bot.stop`
  45. can be used almost anywhere. Both take an optional "reason" that will be
  46. logged and used as the quit message when disconnecting from IRC.
  47. :py:class:`earwigbot.config.BotConfig` stores configuration information for the
  48. bot. Its docstrings explains what each attribute is used for, but essentially
  49. each "node" (one of :py:attr:`config.components
  50. <earwigbot.config.BotConfig.components>`,
  51. :py:attr:`~earwigbot.config.BotConfig.wiki`,
  52. :py:attr:`~earwigbot.config.BotConfig.irc`,
  53. :py:attr:`~earwigbot.config.BotConfig.commands`,
  54. :py:attr:`~earwigbot.config.BotConfig.tasks`, or
  55. :py:attr:`~earwigbot.config.BotConfig.metadata`) maps to a section
  56. of the bot's :file:`config.yml` file. For example, if :file:`config.yml`
  57. includes something like::
  58. irc:
  59. frontend:
  60. nick: MyAwesomeBot
  61. channels:
  62. - "##earwigbot"
  63. - "#channel"
  64. - "#other-channel"
  65. ...then :py:attr:`config.irc["frontend"]["nick"]` will be ``"MyAwesomeBot"``
  66. and :py:attr:`config.irc["frontend"]["channels"]` will be
  67. ``["##earwigbot", "#channel", "#other-channel"]``.
  68. Custom IRC commands
  69. -------------------
  70. Custom commands are subclasses of :py:class:`earwigbot.commands.Command` that
  71. override :py:class:`~earwigbot.commands.Command`'s
  72. :py:meth:`~earwigbot.commands.Command.process` (and optionally
  73. :py:meth:`~earwigbot.commands.Command.check` or
  74. :py:meth:`~earwigbot.commands.Command.setup`) methods.
  75. :py:class:`~earwigbot.commands.Command`'s docstrings should explain what each
  76. attribute and method is for and what they should be overridden with, but these
  77. are the basics:
  78. - Class attribute :py:attr:`~earwigbot.commands.Command.name` is the name of
  79. the command. This must be specified.
  80. - Class attribute :py:attr:`~earwigbot.commands.Command.commands` is a list of
  81. names that will trigger this command. It defaults to the command's
  82. :py:attr:`~earwigbot.commands.Command.name`, but you can override it with
  83. multiple names to serve as aliases. This is handled by the default
  84. :py:meth:`~earwigbot.commands.Command.check` implementation (see below), so
  85. if :py:meth:`~earwigbot.commands.Command.check` is overridden, this is
  86. ignored by everything except the help_ command (so ``!help alias`` will
  87. trigger help for the actual command).
  88. - Class attribute :py:attr:`~earwigbot.commands.Command.hooks` is a list of the
  89. "IRC events" that this command might respond to. It defaults to ``["msg"]``,
  90. but options include ``"msg_private"`` (for private messages only),
  91. ``"msg_public"`` (for channel messages only), and ``"join"`` (for when a user
  92. joins a channel). See the afc_status_ plugin for a command that responds to
  93. other hook types.
  94. - Method :py:meth:`~earwigbot.commands.Command.setup` is called *once* with no
  95. arguments immediately after the command is first loaded. Does nothing by
  96. default; treat it like an :py:meth:`__init__` if you want
  97. (:py:meth:`~earwigbot.tasks.Command.__init__` does things by default and a
  98. dedicated setup method is often easier than overriding
  99. :py:meth:`~earwigbot.tasks.Command.__init__` and using :py:obj:`super`).
  100. - Method :py:meth:`~earwigbot.commands.Command.check` is passed a
  101. :py:class:`~earwigbot.irc.data.Data` object, and should return ``True`` if
  102. you want to respond to this message, or ``False`` otherwise. The default
  103. behavior is to return ``True`` only if :py:attr:`data.is_command` is ``True``
  104. and :py:attr:`data.command` ``==``
  105. :py:attr:`~earwigbot.commands.Command.name` (or :py:attr:`data.command
  106. <earwigbot.irc.data.Data.command>` is in
  107. :py:attr:`~earwigbot.commands.Command.commands` if that list is overriden;
  108. see above), which is suitable for most cases. A possible reason for
  109. overriding is if you want to do something in response to events from a
  110. specific channel only. Note that by returning ``True``, you prevent any other
  111. commands from responding to this message.
  112. - Method :py:meth:`~earwigbot.commands.Command.process` is passed the same
  113. :py:class:`~earwigbot.irc.data.Data` object as
  114. :py:meth:`~earwigbot.commands.Command.check`, but only if
  115. :py:meth:`~earwigbot.commands.Command.check` returned ``True``. This is where
  116. the bulk of your command goes. To respond to IRC messages, there are a number
  117. of methods of :py:class:`~earwigbot.commands.Command` at your disposal. See
  118. the test_ command for a simple example, or look in
  119. :py:class:`~earwigbot.commands.Command`'s
  120. :py:meth:`~earwigbot.commands.Command.__init__` method for the full list.
  121. The most common ones are :py:meth:`say(chan_or_user, msg)
  122. <earwigbot.irc.connection.IRCConnection.say>`, :py:meth:`reply(data, msg)
  123. <earwigbot.irc.connection.IRCConnection.reply>` (convenience function; sends
  124. a reply to the issuer of the command in the channel it was received),
  125. :py:meth:`action(chan_or_user, msg)
  126. <earwigbot.irc.connection.IRCConnection.action>`,
  127. :py:meth:`notice(chan_or_user, msg)
  128. <earwigbot.irc.connection.IRCConnection.notice>`, :py:meth:`join(chan)
  129. <earwigbot.irc.connection.IRCConnection.join>`, and
  130. :py:meth:`part(chan) <earwigbot.irc.connection.IRCConnection.part>`.
  131. Commands have access to :py:attr:`config.commands[command_name]` for config
  132. information, which is a node in :file:`config.yml` like every other attribute
  133. of :py:attr:`bot.config`. This can be used to store, for example, API keys or
  134. SQL connection info, so that these can be easily changed without modifying the
  135. command itself.
  136. The command *class* doesn't need a specific name, but it should logically
  137. follow the command's name. The filename doesn't matter, but it is recommended
  138. to match the command name for readability. Multiple command classes are allowed
  139. in one file.
  140. The bot has a wide selection of built-in commands and plugins to act as sample
  141. code and/or to give ideas. Start with test_, and then check out chanops_ and
  142. afc_status_ for some more complicated scripts.
  143. Custom bot tasks
  144. ----------------
  145. Custom tasks are subclasses of :py:class:`earwigbot.tasks.Task` that
  146. override :py:class:`~earwigbot.tasks.Task`'s
  147. :py:meth:`~earwigbot.tasks.Task.run` (and optionally
  148. :py:meth:`~earwigbot.tasks.Task.setup`) methods.
  149. :py:class:`~earwigbot.tasks.Task`'s docstrings should explain what each
  150. attribute and method is for and what they should be overridden with, but these
  151. are the basics:
  152. - Class attribute :py:attr:`~earwigbot.tasks.Task.name` is the name of the
  153. task. This must be specified.
  154. - Class attribute :py:attr:`~earwigbot.tasks.Task.number` can be used to store
  155. an optional "task number", possibly for use in edit summaries (to be
  156. generated with :py:meth:`~earwigbot.tasks.Task.make_summary`). For
  157. example, EarwigBot's :py:attr:`config.wiki["summary"]` is
  158. ``"([[WP:BOT|Bot]]; [[User:EarwigBot#Task $1|Task $1]]): $2"``, which the
  159. task class's :py:meth:`make_summary(comment)
  160. <earwigbot.tasks.Task.make_summary>` method will take and replace
  161. ``$1`` with the task number and ``$2`` with the details of the edit.
  162. Additionally, :py:meth:`~earwigbot.tasks.Task.shutoff_enabled` (which checks
  163. whether the bot has been told to stop on-wiki by checking the content of a
  164. particular page) can check a different page for each task using similar
  165. variables. EarwigBot's :py:attr:`config.wiki["shutoff"]["page"]` is
  166. ``"User:$1/Shutoff/Task $2"``; ``$1`` is substituted with the bot's username,
  167. and ``$2`` is substituted with the task number, so, e.g., task #14 checks the
  168. page ``[[User:EarwigBot/Shutoff/Task 14]].`` If the page's content does *not*
  169. match :py:attr:`config.wiki["shutoff"]["disabled"]` (``"run"`` by default),
  170. then shutoff is considered to be *enabled* and
  171. :py:meth:`~earwigbot.tasks.Task.shutoff_enabled` will return ``True``,
  172. indicating the task should not run. If you don't intend to use either of
  173. these methods, feel free to leave this attribute blank.
  174. - Method :py:meth:`~earwigbot.tasks.Task.setup` is called *once* with no
  175. arguments immediately after the task is first loaded. Does nothing by
  176. default; treat it like an :py:meth:`__init__` if you want
  177. (:py:meth:`~earwigbot.tasks.Task.__init__` does things by default and a
  178. dedicated setup method is often easier than overriding
  179. :py:meth:`~earwigbot.tasks.Task.__init__` and using :py:obj:`super`).
  180. - Method :py:meth:`~earwigbot.tasks.Task.run` is called with any number of
  181. keyword arguments every time the task is executed (by
  182. :py:meth:`tasks.start(task_name, **kwargs)
  183. <earwigbot.managers.TaskManager.start>`, usually). This is where the bulk of
  184. the task's code goes. For interfacing with MediaWiki sites, read up on the
  185. :doc:`Wiki Toolset <toolset>`.
  186. Tasks have access to :py:attr:`config.tasks[task_name]` for config information,
  187. which is a node in :file:`config.yml` like every other attribute of
  188. :py:attr:`bot.config`. This can be used to store, for example, edit summaries
  189. or templates to append to user talk pages, so that these can be easily changed
  190. without modifying the task itself.
  191. The task *class* doesn't need a specific name, but it should logically follow
  192. the task's name. The filename doesn't matter, but it is recommended to match
  193. the task name for readability. Multiple tasks classes are allowed in one file.
  194. See the built-in wikiproject_tagger_ task for a relatively straightforward
  195. task, or the afc_statistics_ plugin for a more complicated one.
  196. .. _help: https://github.com/earwig/earwigbot/blob/develop/earwigbot/commands/help.py
  197. .. _afc_status: https://github.com/earwig/earwigbot-plugins/blob/develop/commands/afc_status.py
  198. .. _test: https://github.com/earwig/earwigbot/blob/develop/earwigbot/commands/test.py
  199. .. _chanops: https://github.com/earwig/earwigbot/blob/develop/earwigbot/commands/chanops.py
  200. .. _wikiproject_tagger: https://github.com/earwig/earwigbot/blob/develop/earwigbot/tasks/wikiproject_tagger.py
  201. .. _afc_statistics: https://github.com/earwig/earwigbot-plugins/blob/develop/tasks/afc_statistics.py