indivo package¶
Subpackages¶
- indivo.data_models package
- indivo.fields package
- indivo.rdf package
- indivo.serializers package
- indivo.views package
- Subpackages
- indivo.views.documents package
- Submodules
- indivo.views.documents.document module
- indivo.views.documents.document_delete module
- indivo.views.documents.document_label module
- indivo.views.documents.document_meta module
- indivo.views.documents.document_rels module
- indivo.views.documents.document_status module
- indivo.views.documents.document_versions module
- indivo.views.documents.special_documents module
- Module contents
- indivo.views.reports package
- indivo.views.shares package
- indivo.views.documents package
- Submodules
- indivo.views.account module
- indivo.views.audit module
- indivo.views.base module
- indivo.views.messaging module
- indivo.views.pha module
- indivo.views.record module
- indivo.views.smart_container module
- Module contents
- Subpackages
Submodules¶
indivo.settings_rtfd module¶
indivo.validators module¶
Validators useful for attaching to data models.
- class indivo.validators.ExactValueValidator(valid_value, nullable=False)¶
Bases: indivo.validators.ValueInSetValidator
Validates that a value is exactly equal to a certain value.
The optional ‘nullable’ flag determines whether or not the value may also be empty.
- class indivo.validators.NonNullValidator¶
Bases: object
Validates that a value is not null.
A ‘null’ value is anything that Django would store as NULL in a database: None, "", [], (), or {}. Note that other python objects that evaluate to false (0, False) are not actually null values, as they represent data.
This validator is useful for validating that strings are non-empty, for example.
- class indivo.validators.ValueInSetValidator(valid_values, nullable=False)¶
Bases: object
Validates that a value is within a set of possible values.
The optional ‘nullable’ flag determines whether or not the value may also be empty.
indivo.wsgi module¶
WSGI config for indivo project.
This module contains the WSGI application used by Django’s development server and any production WSGI deployments. It should expose a module-level variable named application. Django’s runserver and runfcgi commands discover this application via the WSGI_APPLICATION setting.
Usually you will have the standard Django WSGI application here, but it also might make sense to replace the whole Django WSGI application with a custom one that later delegates to the Django one. For example, you could introduce WSGI middleware here, or combine a Django application with an application of another framework.