lories.core.activator
=====================

.. py:module:: lories.core.activator

.. autoapi-nested-parse::

   lories.core.activator
   ~~~~~~~~~~~~~~~~~~~~~




Classes
-------

.. autoapisummary::

   lories.core.activator.Activator
   lories.core.activator.ActivatorMeta


Module Contents
---------------

.. py:class:: Activator(configs: Optional[lories._core._configurations.Configurations] = None, logger: Optional[logging.Logger] = None, **kwargs)

   Bases: :py:obj:`lories._core._activator._Activator`, :py:obj:`lories.core.configs.configurator.Configurator`

   .. autoapi-inheritance-diagram:: lories.core.activator.Activator
      :parts: 1
      :private-bases:


   Helper class that provides a standard way to create an ABC using
   inheritance.


.. py:class:: ActivatorMeta

   Bases: :py:obj:`lories.core.configs.configurator.ConfiguratorMeta`

   .. autoapi-inheritance-diagram:: lories.core.activator.ActivatorMeta
      :parts: 1
      :private-bases:


   Metaclass for defining Abstract Base Classes (ABCs).

   Use this metaclass to create an ABC.  An ABC can be subclassed
   directly, and then acts as a mix-in class.  You can also register
   unrelated concrete classes (even built-in classes) and unrelated
   ABCs as 'virtual subclasses' -- these and their descendants will
   be considered subclasses of the registering ABC by the built-in
   issubclass() function, but the registering ABC won't show up in
   their MRO (Method Resolution Order) nor will method
   implementations defined by the registering ABC be callable (not
   even via super()).