Django Exceptions

Django raises some of its own exceptions as well as standard Python exceptions.

Django Core Exceptions

Django core exception classes are defined in django.core.exceptions.

AppRegistryNotReady

  • exception AppRegistryNotReady[source]
  • This exception is raised when attempting to use models before the apploading process, which initializes the ORM, iscomplete.

ObjectDoesNotExist

  • exception ObjectDoesNotExist[source]
  • The base class for DoesNotExist exceptions;a try/except for ObjectDoesNotExist will catchDoesNotExist exceptions for all models.

See get() for further informationon ObjectDoesNotExist and DoesNotExist.

EmptyResultSet

  • exception EmptyResultSet[source]
  • EmptyResultSet may be raised during query generation if a query won'treturn any results. Most Django projects won't encounter this exception,but it might be useful for implementing custom lookups and expressions.

Changed in Django 1.11:In older versions, it's only importable from django.db.models.sql.

FieldDoesNotExist

  • exception FieldDoesNotExist[source]
  • The FieldDoesNotExist exception is raised by a model's_meta.get_field() method when the requested field does not exist on themodel or on the model's parents.

MultipleObjectsReturned

  • exception MultipleObjectsReturned[source]
  • The MultipleObjectsReturned exception is raised by a query if onlyone object is expected, but multiple objects are returned. A base versionof this exception is provided in django.core.exceptions; each modelclass contains a subclassed version that can be used to identify thespecific object type that has returned multiple objects.

See get() for further information.

SuspiciousOperation

  • exception SuspiciousOperation[source]

  • The SuspiciousOperation exception is raised when a user hasperformed an operation that should be considered suspicious from a securityperspective, such as tampering with a session cookie. Subclasses ofSuspiciousOperation include:

    • DisallowedHost
    • DisallowedModelAdminLookup
    • DisallowedModelAdminToField
    • DisallowedRedirect
    • InvalidSessionKey
    • RequestDataTooBig
    • SuspiciousFileOperation
    • SuspiciousMultipartForm
    • SuspiciousSession
    • TooManyFieldsSentIf a SuspiciousOperation exception reaches the WSGI handler level it islogged at the Error level and results ina HttpResponseBadRequest. See the loggingdocumentation for more information.

PermissionDenied

  • exception PermissionDenied[source]
  • The PermissionDenied exception is raised when a user does not havepermission to perform the action requested.

ViewDoesNotExist

MiddlewareNotUsed

  • exception MiddlewareNotUsed[source]
  • The MiddlewareNotUsed exception is raised when a middleware is notused in the server configuration.

ImproperlyConfigured

  • exception ImproperlyConfigured[source]
  • The ImproperlyConfigured exception is raised when Django issomehow improperly configured — for example, if a value in settings.pyis incorrect or unparseable.

FieldError

  • exception FieldError[source]

  • The FieldError exception is raised when there is a problem with amodel field. This can happen for several reasons:

    • A field in a model clashes with a field of the same name from anabstract 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 queryparameters
    • A join is not permitted on the specified field
    • A field name is invalid
    • A query contains invalid order_by arguments

ValidationError

NON_FIELD_ERRORS

  • NON_FIELD_ERRORS
  • ValidationErrors that don't belong to a particular field in a formor model are classified as NON_FIELD_ERRORS. This constant is usedas a key in dictionaries that otherwise map fields to their respectivelist of errors.

URL Resolver exceptions

URL Resolver exceptions are defined in django.urls.

Resolver404

NoReverseMatch

  • exception NoReverseMatch[source]
  • The NoReverseMatch exception is raised by django.urls when amatching URL in your URLconf cannot be identified based on the parameterssupplied.

Database Exceptions

Database exceptions may be imported from django.db.

Django wraps the standard database exceptions so that your Django code has aguaranteed common implementation of these classes.

  • exception Error[source]
  • exception InterfaceError[source]
  • exception DatabaseError[source]
  • exception DataError[source]
  • exception OperationalError[source]
  • exception IntegrityError[source]
  • exception InternalError[source]
  • exception ProgrammingError[source]
  • exception NotSupportedError[source]
  • The Django wrappers for database exceptions behave exactly the same asthe underlying database exceptions. See PEP 249, the Python Database APISpecification v2.0, for further information.

As per PEP 3134, a cause attribute is set with the original(underlying) database exception, allowing access to any additionalinformation provided.

Http Exceptions

Http exceptions may be imported from django.http.

UnreadablePostError

Transaction Exceptions

Transaction exceptions are defined in django.db.transaction.

TransactionManagementError

Testing Framework Exceptions

Exceptions provided by the django.test package.

RedirectCycleError

  • exception client.RedirectCycleError
  • RedirectCycleError is raised when the test client detects aloop or an overly long chain of redirects.

Python Exceptions

Django raises built-in Python exceptions when appropriate as well. See thePython documentation for further information on the Built-in Exceptions.