doc/api/cwvreg.rst
author David Douard <david.douard@logilab.fr>
Tue, 03 Mar 2015 12:26:47 +0100
changeset 11152 fccc6ddd975c
parent 10499 d0907690af55
child 12813 9c151701d63e
permissions -rw-r--r--
[skeleton] do not import the __pkginfo__.py module to make cubes installable via setuptools When using a simple "import" statement, running 'python setup.py install' for a cube fails in a fresh virtualenv due to the fact the install of the dependencies (here cubicweb iteself) is done by the python process doing the cube's installation, so the __pkginfo__ module from the cube is already loaded (thus used) when installing cubicweb... So we apply the third technique from: https://packaging.python.org/en/latest/single_source_version.html

.. _cwvreg_module:

:mod:`cubicweb.cwvreg`
======================

.. automodule:: cubicweb.cwvreg

    .. autoclass:: CWRegistryStore
        :show-inheritance:
        :members:
        :undoc-members:

    .. autoclass:: CWRegistry
        :show-inheritance:
        :members: schema, poss_visible_objects, select

    .. autoclass:: InstancesRegistry
        :show-inheritance:
        :members:

    .. autoclass:: ETypeRegistry
        :show-inheritance:
        :members:

    .. autoclass:: ViewsRegistry
        :show-inheritance:
        :members:

    .. autoclass:: ActionsRegistry
        :show-inheritance:
        :members:

    .. autoclass:: CtxComponentsRegistry
        :show-inheritance:
        :members:

    .. autoclass:: BwCompatCWRegistry
        :show-inheritance:
        :members:


:mod:`logilab.common.registry`
==============================

.. automodule:: logilab.common.registry