Fixed #31008 -- Fixed typos in docs/topics/logging.txt.

This commit is contained in:
Mariusz Felisiak 2019-11-20 20:35:36 +01:00 committed by GitHub
parent 36453526d3
commit 3e5b349535
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions

View File

@ -240,9 +240,9 @@ is the best source of information about logging configuration dictionaries.
However, to give you a taste of what is possible, here are several examples. However, to give you a taste of what is possible, here are several examples.
First, here's a configuration which writes all logging from the First, here's a configuration which writes all logging from the
:ref:`django-logger` logger to a local file:: :ref:`django-logger` logger to a local file:
.. code-block:: python .. code-block:: python
:caption: settings.py :caption: settings.py
LOGGING = { LOGGING = {
@ -275,9 +275,9 @@ console (same as Django's default logging config, except that the default only
displays log records when ``DEBUG=True``). Django does not log many such displays log records when ``DEBUG=True``). Django does not log many such
messages. With this config, however, you can also set the environment variable messages. With this config, however, you can also set the environment variable
``DJANGO_LOG_LEVEL=DEBUG`` to see all of Django's debug logging which is very ``DJANGO_LOG_LEVEL=DEBUG`` to see all of Django's debug logging which is very
verbose as it includes all database queries:: verbose as it includes all database queries:
.. code-block:: python .. code-block:: python
:caption: settings.py :caption: settings.py
import os import os
@ -298,9 +298,9 @@ verbose as it includes all database queries::
}, },
} }
Finally, here's an example of a fairly complex logging setup:: Finally, here's an example of a fairly complex logging setup:
.. code-block:: python .. code-block:: python
:caption: settings.py :caption: settings.py
LOGGING = { LOGGING = {