Pluggage
A Utility library for using plugins with python There are two ways to use this library to dynamically load objects, a lightweight load-on-demand via a dictionary interface and a heavier factory pattern using a base class to register objects with a factory.
Lightweight Plugins
The lightweight plugin system uses a dictionary API to load dot-delimited names and either return the object or optionally call it.
from pluggage.plugins import Plugins
loader = Plugins()
# load references to objects
func_ref = loader['some_module.some_submodule.some_function']
cls_ref = loader['some_module.some_submodule.SomeClass']
# call the objects and get the results
func_result = loader('some_module.some_submodule.some_function', *func_args, **func_kwargs)
someclass_instance = loader('some_module.some_submodule.SomeClass', *ctor_args, **ctor_kwargs)
Heavyweight Plugins
The Heavyweight Plugins are implemented via a metaclass registry that allows classes to be registered as plugins on import, and then accessed via a named factory. Classes inheriting from the base plugin class specify which factory they will be registered with and by default will register under that factory with their class name, or that can also be overridden by inheritance. The plugins can be accessed using a get_factory call provided in the pluggage.registry module.
factory = get_factory('my_factory')
some_class_instance = factory('SomeClass', *ctor_args, **ctor_kwargs)
To register a class with a factory, inherit from the PluggagePlugin class and set the PLUGGAGE_FACTORY_NAME class attribute:
from pluggage.factory_plugin import PluggagePlugin
class SomeClass(PluggagePlugin):
"""
sample plugin
"""
PLUGGAGE_FACTORY_NAME = 'my_factory'
def __init__(self, value):
self.value = value
def __call__(self):
print(value)
factory = get_factory('my_factory')
some_class_instance = factory('SomeClass', 'abc')
some_class_instance() # prints 'abc'
Metadata
Release files for pluggage 0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pluggage-0.0.4.tar.gz | 5.0 kB | Without provenance | Details for pluggage-0.0.4.tar.gz |
Release files / pluggage-0.0.4.tar.gz
| Download URL | pluggage-0.0.4.tar.gz |
|---|---|
| Size | 5.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3eeb940344f72ffd99e9568fe9f9588707952f2b626143df62dfe056c75316fc
|
|
BLAKE2b-256 checksum How to use checksums |
968f38f2322af6f6204e6c01eba7a6cee7b691f0e8180806b4a9175d6731387d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pluggage 0.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.