Custom chula exceptions
Chula exception class which adds additional functionality to aid in efficiently raising custom exceptions.
Getter for a message property, to avoid using an attribute named “message” which will raise deprecation errors in Python-2.6.
When the msg method is not overloaded, return a generic message
Exception indicating the requested controller class not found.
Exception while trying to import the controller.
Exception indicating the requested controller method not found.
Exception indicating that a controller method is returning None, which is probably not on purpose. It’s true that we do cast all output as a string, thus None is technically valid, it’s most likely that the controller method simply forgot to return. This will save time by pointing this out. If you really need to return None, then return: ‘None’
Exception indicating the requested module method not found.
Exception indicating that the controller was unable to perform the requested redirect.
Exception indicating an invalid attribute was used.
Exception indicating an invalid key was used against a cache source.
Exception indicating an invalid key was used against a restricted collection class.
Exception indicating that the database connection string used is invalid.
Exception indicating that the password used does not meet minimum requirements (aka: isn’t strong enough).
Exception indicating a required dependency of chula is either missing or of an incompatible version.
It is illegal to remove a key from a RestrictedCollection object.
Exception indicating that a restricted attribute was not given a default value.
Chula is unable to persist either to PostgreSQL or Memached.
Exception indicating that the requested data type conversion was not possible.
Exception indicating a requst for an unsupported database engine
Exception indicating an invalid mapper configuration
Exception indicating the chula api is being misused.
Exception indicating that the specified webservice transport is either unknown or unsupported.