If you want to learn how to make Mopidy extensions, read Extension development.
Base class for Mopidy extensions
The extension’s distribution name, as registered on PyPI
Example: Mopidy-Soundspot
The extension’s short name, as used in setup.py and as config section name
Example: soundspot
List of backend actor classes
Mopidy will take care of starting the actors.
Returns: | list of Backend subclasses |
---|
Command to expose to command line users running mopidy.
Returns: | Instance of a Command class. |
---|
The extension’s default config as a bytestring
Returns: | bytes or unicode |
---|
List of frontend actor classes
Mopidy will take care of starting the actors.
Returns: | list of pykka.Actor subclasses |
---|
List of library updater classes
Returns: | list of BaseLibraryUpdateProvider subclasses |
---|
Hook for registering custom GStreamer elements
Register custom GStreamer elements by implementing this method. Example:
def register_gstreamer_elements(self):
from .mixer import SoundspotMixer
gobject.type_register(SoundspotMixer)
gst.element_register(
SoundspotMixer, 'soundspotmixer', gst.RANK_MARGINAL)
Returns: | None |
---|
Checks if the extension can run in the current environment
For example, this method can be used to check if all dependencies that are needed are installed.
Raises: | ExtensionError |
---|---|
Returns: | None |
The extension’s version
Should match the __version__ attribute on the extension’s main Python module and the version registered on PyPI.
Find all installed extensions.
Returns: | list of installed extensions |
---|