Fixed #14388 -- Corrected some typos in the logging docs. Thanks to varikin,...

A tuple of directories where Django looks for translation files.

See :ref:`using-translations-in-your-own-projects`.

.. setting:: LOGIN_REDIRECT_URL

.. setting:: LOGGING

LOGGING

-------

.. versionadded:: 1.3

Default: A logging configuration dictionary.

A data structure containing configuration information. The contents of

The default logging configuration passes HTTP 500 server errors to an

email log handler; all other log messages are given to a NullHandler.

.. versionadded:: 1.3

.. setting:: LOGGING_CONFIG

LOGGING_CONFIG

--------------

.. versionadded:: 1.3

Default: ``'django.utils.log.dictConfig'``

A path to a callable that will be used to configure logging in the

.. _dictConfig: http://docs.python.org/library/logging.html#logging.dictConfig

.. versionadded:: 1.3

.. setting:: LOGIN_REDIRECT_URL

LOGIN_REDIRECT_URL

------------------

A logger is the entry point into the logging system. Each logger is

a named bucket to which messages can be written for processing.

A logger is configured to have *log level*. This log level describes

A logger is configured to have a *log level*. This log level describes

the severity of the messages that the logger will handle. Python

defines the following log levels:

stack trace or an error code.

When a message is given to the logger, the log level of the message is

compare to the log level of the logger. If the log level of the

compared to the log level of the logger. If the log level of the

message meets or exceeds the log level of the logger itself, the

message will undergo further processing. If it doesn't, the message

will be ignored.

different log level. In this way, it is possible to provide different

forms of notification depending on the importance of a message. For

example, you could install one handler that forwards ``ERROR`` and

``CRITICIAL`` messages to a paging service, while a second handler

``CRITICAL`` messages to a paging service, while a second handler

logs all messages (including ``ERROR`` and ``CRITICAL`` messages) to a

file for later analysis.

error log record will be written.

Naming loggers

~~~~~~~~~~~~~~

--------------

The call to :meth:`logging.getLogger()` obtains (creating, if

necessary) an instance of a logger. The logger instance is identified

can turn off this behavior.

Making logging calls

~~~~~~~~~~~~~~~~~~~~

--------------------

The logger instance contains an entry method for each of the default

log levels:

There are two other logging calls available:

    * ``logger.log()``: manually a logging message with a specific

      log level.

    * ``logger.log()``: Manually emits a logging message with a

      specific log level.

    * ``logger.exception()``: create a ``ERRORR`` level logging

    * ``logger.exception()``: Creates an ``ERORR`` level logging

      message wrapping the current exception stack frame.

Configuring logging

formatters to ensure that logging output is output in a useful way.

Python's logging library provides several techniques to configure

logging, ranging from a programatic interface to configuration files.

logging, ranging from a programmatic interface to configuration files.

By default, Django uses the `dictConfig format`_.

.. note::

    * Defines three handlers:

        * ``null``, a NullHandler, which will pass any `DEBUG` or

        * ``null``, a NullHandler, which will pass any ``DEBUG`` or

          higher message to ``/dev/null``.

        * ``console``, a StreamHandler, which will print any `DEBUG`

        * ``console``, a StreamHandler, which will print any ``DEBUG``

          message to stdout. This handler uses the `simple` output

          format.

        * ``mail_admins``, an AdminEmailHandler, which will email any

          `ERROR` level message to the site admins. This handler uses

          ``ERROR`` level message to the site admins. This handler uses

          the ``special`` filter.

    * Configures three loggers:

          or higher that also pass the ``special`` filter to two

          handlers -- the ``console``, and ``mail_admins``. This

          means that all ``INFO`` level messages (or higher) will be

          printed to the console; ``ERROR`` and ``CRITICIAL``

          printed to the console; ``ERROR`` and ``CRITICAL``

          messages will also be output via e-mail.

.. _formatter documentation: http://docs.python.org/library/logging.html#formatter-objects