Skip to content

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() raise NotImplementedError for a hook with a wrapper.
  • Asynchronous loading. load(), load_all() and unload() 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() with cache=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=True cannot be called directly (Pluggy refuses), and call_historic is not reachable through pm.hook.
  • enable() after should_load() declined. A plugin that declined to load is in state DISABLED; calling pm.enable() on it marks it LOADED and puts its hooks in dispatch although its load() never ran. Do not call enable() on a plugin you did not disable().
  • A plugin whose requirement fails stays INSTANTIATED, with no error recorded on it: pm.error() returns None for it. Look at its requirements' states.
  • Function plugins share their identity attributes. Plugins written with @plugin report the namespace and name of 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 index skips modules that fail to import without saying so.
  • on_resolve_error is declared on LifecycleListener but never called.