Django raises some of its own exceptions as well as standard Python exceptions.
Django Core Exceptions¶
Django core exception classes are defined in
EmptyResultSetmay be raised during query generation if a query won’t return any results. Most Django projects won’t encounter this exception, but it might be useful for implementing custom lookups and expressions.Changed in Django Development version:
In older versions, it’s only importable from
FieldDoesNotExistexception is raised by a model’s
_meta.get_field()method when the requested field does not exist on the model or on the model’s parents.
MultipleObjectsReturnedexception 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.
get()for further information.
SuspiciousOperationexception 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. Subclasses of
FieldErrorexception is raised when there is a problem with a model field. This can happen for several reasons:
- A field in a model clashes with a field of the same name from an abstract base class
- An infinite loop is caused by ordering
- A keyword cannot be parsed from the filter parameters
- A field cannot be determined from a keyword in the query parameters
- A join is not permitted on the specified field
- A field name is invalid
- A query contains invalid order_by arguments
URL Resolver exceptions¶
URL Resolver exceptions are defined in
Deprecated since version 1.10: In older versions, these exceptions are located in
django.core.urlresolvers. Importing from the old location will continue
to work until Django 2.0.
Database exceptions may be imported from
Django wraps the standard database exceptions so that your Django code has a guaranteed common implementation of these classes.
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.
As per PEP 3134, a
__cause__ attribute is set with the original
(underlying) database exception, allowing access to any additional
information provided. (Note that this attribute is available under
both Python 2 and Python 3, although PEP 3134 normally only applies
to Python 3. To avoid unexpected differences with Python 3, Django will also
ensure that the exception made available via
__cause__ has a usable
__traceback__ attribute described above was added.
Http exceptions may be imported from
Transaction exceptions are defined in
Testing Framework Exceptions¶
Exceptions provided by the