Lines Matching refs:plugins

9 "plugins" and register themselves as ``pw`` commands as well. After activating
48 Registering ``pw`` plugins
51 plugins are registered by providing the command name, module, and function in a
53 built-in commands. Since they are accessed by module name, plugins must be
59 Registered plugins appear as commands in the ``pw`` tool when ``pw`` is run from
97 so plugins can behave the same whether they are executed independently or
279 pw_cli.plugins
281 :py:mod:`pw_cli.plugins` provides general purpose plugin functionality. The
282 module can be used to create plugins for command line tools, interactive
284 plugins.
286 To use plugins, create a :py:class:`pw_cli.plugins.Registry`. The registry may
287 have an optional validator function that checks plugins before they are
288 registered (see :py:meth:`pw_cli.plugins.Registry.__init__`).
292  * **Direct function call.** Register plugins by calling
293    :py:meth:`pw_cli.plugins.Registry.register` or
294    :py:meth:`pw_cli.plugins.Registry.register_by_name`.
298      registry = pw_cli.plugins.Registry()
303  * **Decorator.** Register using the :py:meth:`pw_cli.plugins.Registry.plugin`
308      _REGISTRY = pw_cli.plugins.Registry()
334    :py:meth:`pw_cli.plugins.Registry.register_file` and
335    :py:meth:`pw_cli.plugins.Registry.register_directory`.
337 pw_cli.plugins module reference  argument
339 .. automodule:: pw_cli.plugins