lories.application.interface
============================

.. py:module:: lories.application.interface

.. autoapi-nested-parse::

   lories.application.interface
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~




Exceptions
----------

.. autoapisummary::

   lories.application.interface.InterfaceException


Classes
-------

.. autoapisummary::

   lories.application.interface.Interface
   lories.application.interface.InterfaceMeta


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

.. py:exception:: InterfaceException

   Bases: :py:obj:`lories.core.ResourceError`

   .. autoapi-inheritance-diagram:: lories.application.interface.InterfaceException
      :parts: 1
      :private-bases:


   Raise if an error occurred accessing the interface.


   Initialize self.  See help(type(self)) for accurate signature.


.. py:class:: Interface(context: lories._core._data.DataContext, configs: lories._core._configurations.Configurations, **kwargs)

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

   .. autoapi-inheritance-diagram:: lories.application.interface.Interface
      :parts: 1
      :private-bases:


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


.. py:class:: InterfaceMeta

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

   .. autoapi-inheritance-diagram:: lories.application.interface.InterfaceMeta
      :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()).