Known Limitations¶
pluxeo is pre-release. This page lists what does not work yet, so that nobody has to find out the hard way. Each item will be removed from this page when it is fixed.
Not supported, by design¶
- Async hook wrappers.
.aio()and.aio_gather()raiseNotImplementedErrorfor a hook with a wrapper. - Asynchronous loading.
load(),load_all()andunload()are synchronous. - File-system watching. New plugins are picked up only when the host calls
refresh(). - Several versions of one plugin, and re-resolving dependencies when a plugin is replaced at runtime.
- Dependency injection and scoped instances. One instance per plugin per manager, or one per
load()withcache=False. Every instance is created through its spec's factory, so a container can take over that step in a later version.
Known issues¶
- Historic hooks cannot be called. A hookspec with
historic=Truecannot be called directly (Pluggy refuses), andcall_historicis not reachable throughpm.hook. enable()aftershould_load()declined. A plugin that declined to load is in stateDISABLED; callingpm.enable()on it marks itLOADEDand puts its hooks in dispatch although itsload()never ran. Do not callenable()on a plugin you did notdisable().- A plugin whose requirement fails stays
INSTANTIATED, with no error recorded on it:pm.error()returnsNonefor it. Look at its requirements' states. - Function plugins share their identity attributes. Plugins written with
@pluginreport thenamespaceandnameof the most recently created function plugin when read from the plugin object. The manager does not use those attributes to find or name plugins, but contract error messages do. pluxeo indexskips modules that fail to import without saying so.on_resolve_erroris declared onLifecycleListenerbut never called.