Django raises some Django specific exceptions as well as many standard Python exceptions.
The DoesNotExist exception is raised when an object is not found for the given parameters of a query.
ObjectDoesNotExist is defined in django.core.exceptions. DoesNotExist is a subclass of the base ObjectDoesNotExist exception that is provided on every model class as a way of identifying the specific type of object that could not be found.
See get() for further information on ObjectDoesNotExist and DoesNotExist.
The MultipleObjectsReturned exception is raised by a query if only one object is expected, but multiple objects are returned. A base version of this exception is provided in django.core.exceptions; each model class contains a subclassed version that can be used to identify the specific object type that has returned multiple objects.
See get() for further information.
The SuspiciousOperation exception is raised when a user has performed an operation that should be considered suspicious from a security perspective, such as tampering with a session cookie.
The PermissionDenied exception is raised when a user does not have permission to perform the action requested.
The ViewDoesNotExist exception is raised by django.core.urlresolvers when a requested view does not exist.
The MiddlewareNotUsed exception is raised when a middleware is not used in the server configuration.
The ImproperlyConfigured exception is raised when Django is somehow improperly configured – for example, if a value in settings.py is incorrect or unparseable.
The FieldError exception is raised when there is a problem with a model field. This can happen for several reasons:
The ValidationError exception is raised when data fails form or model field validation. For more information about validation, see Form and Field Validation, Model Field Validation and the Validator Reference.
The NoReverseMatch exception is raised by django.core.urlresolvers when a matching URL in your URLconf cannot be identified based on the parameters supplied.
Django wraps the standard database exceptions DatabaseError and IntegrityError so that your Django code has a guaranteed common implementation of these classes. These database exceptions are provided in django.db.
The Django wrappers for database exceptions behave exactly the same as the underlying database exceptions. See PEP 249, the Python Database API Specification v2.0, for further information.
The TransactionManagementError is raised for any and all problems related to database transactions. It is available from django.db.transaction.
Django raises built-in Python exceptions when appropriate as well. See the Python documentation for further information on the built-in exceptions.
Dec 23, 2012