Plugins are validated when they are imported
Plugins can be loaded through different mechanisms (modules, filesystem paths, entry points_)
Multiple versions_ of the same plugin are supported (The newest one is used by default)
Plugins can be blacklisted_ by type, name, or version
Multiple plugin groups_ are supported so one program can use multiple sets of plugins that won't conflict
Plugins support conditional loading_ (examples: os, version, installed software, etc)
Once loaded, plugins can be accessed_ through dictionary or dot notation

Installation

PIP

.. code-block:: console

$ pip install pluginlib

Fedora and EL (RHEL/CentOS/Rocky/Alma) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

(EPEL_ repositories must be configured_ for EL8)

.. code-block:: console

$ dnf install python3-pluginlib

EL7 (RHEL/CentOS) ^^^^^^^^^^^^^^^^^

(EPEL_ repositories must be configured_)

.. code-block:: console

$ yum install python2-pluginlib
$ yum install python36-pluginlib

Usage

Step 1: Define plugin parent classes

All plugins are subclasses of parent classes. To create a parent class, use the @Parent_ decorator.

The @Parent_ decorator can take a plugin type for accessing child plugins of the parent. If a plugin type isn't given, the class name will be used.

The @Parent_ decorator can also take a group keyword which restricts plugins to a specific plugin group. group should be specified if plugins for different projects could be accessed in an single program, such as with libraries and frameworks. For more information, see the Plugin Groups_ section.

Methods required in child plugins should be labeled as abstract methods. Plugins without these methods or with parameters that don't match, will not be loaded. For more information, see the Abstract Methods_ section.

.. code-block:: python

"""
sample.py
"""
import pluginlib

@pluginlib.Parent('parser')
class Parser(object):

    @pluginlib.abstractmethod
    def parse(self, string):
        pass

Step 2: Define plugin classes

To create a plugin, subclass a parent class and include any required methods.

Plugins can be customized through optional class attributes:

`_alias_`_
    Changes the name of the plugin which defaults to the class name.

`_version_`_
    Sets the version of the plugin. Defaults to the module ``__version__`` or ``None``
    If multiple plugins with the same type and name are loaded, the plugin with
    the highest version is used. For more information, see the Versions_ section.

`_skipload_`_
    Specifies the plugin should not be loaded. This is useful when a plugin is a parent class
    for additional plugins or when a plugin should only be loaded under certain conditions.
    For more information see the `Conditional Loading`_ section.

.. code-block:: python

"""
sample_plugins.py
"""
import json
import sample

class JSON(sample.Parser):

    _alias_ = 'json'

    def parse(self, string):
        return json.loads(string)

Step 3: Load plugins

Plugins are loaded when the module they are in is imported. PluginLoader_ will load modules from specified locations and provides access to them.

PluginLoader_ can load plugins from several locations. - A program's standard library - Entry points_ - A list of modules - A list of filesystem paths

Plugins can also be filtered through blacklists and type filters. See the Blacklists_ and Type Filters_ sections for more information.

Plugins are accessible through the PluginLoader.plugins_ property, a nested dictionary accessible through dot notation. For other ways to access plugins, see the Accessing Plugins_ section.

.. code-block:: python

import pluginlib
import sample

loader = pluginlib.PluginLoader(modules=['sample_plugins'])
plugins = loader.plugins
parser = plugins.parser.json()
print(parser.parse('{"json": "test"}'))

.. _Entry points: https://packaging.python.org/specifications/entry-points/

.. _PluginLoader: http://pluginlib.readthedocs.io/en/stable/api.html#pluginlib.PluginLoader .. _PluginLoader.plugins: http://pluginlib.readthedocs.io/en/stable/api.html#pluginlib.PluginLoader.plugins .. _@Parent: http://pluginlib.readthedocs.io/en/stable/api.html#pluginlib.Parent .. _alias_: http://pluginlib.readthedocs.io/en/stable/api.html#pluginlib.Plugin._alias .. _version_: http://pluginlib.readthedocs.io/en/stable/api.html#pluginlib.Plugin._version .. _skipload_: http://pluginlib.readthedocs.io/en/stable/api.html#pluginlib.Plugin._skipload

.. _EPEL: https://fedoraproject.org/wiki/EPEL .. _configured: https://docs.fedoraproject.org/en-US/epel/#how_can_i_use_these_extra_packages

Keywords

FAQs

What is pluginlib?

Is pluginlib well maintained?

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

pluginlib

Overview

Features

Installation

PIP

Usage

Step 1: Define plugin parent classes

Step 2: Define plugin classes

Step 3: Load plugins

Keywords

Related posts

PyPI Introduces Digital Attestations to Strengthen Python Package Security

GitHub Removes Malicious Pull Requests Targeting Open Source Repositories