From b28b8e2b9a31cdef27c1685ec44b4add65eaa167 Mon Sep 17 00:00:00 2001
From: Ivan Kolodyazhny <e0ne@e0ne.info>
Date: Fri, 26 Jan 2018 11:20:51 +0200
Subject: [PATCH] Change django.utils.log.NullHandler to logging.NullHandler

django.utils.log.NullHandler was removed in Django 1.9. logging.NullHandler
wad added to Python standard library since 2.7 so we should use it now.

Change-Id: I38f3f1d592f5456efc7dc94c0677a0a594722fbd
---
 doc/source/admin/customize-configure.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/source/admin/customize-configure.rst b/doc/source/admin/customize-configure.rst
index 2b8114dc74..1ba7890f19 100644
--- a/doc/source/admin/customize-configure.rst
+++ b/doc/source/admin/customize-configure.rst
@@ -268,7 +268,7 @@ The standard installation uses a non-encrypted HTTP channel.
               'handlers': {
                   'null': {
                       'level': 'DEBUG',
-                      'class': 'django.utils.log.NullHandler',
+                      'class': 'logging.NullHandler',
                       },
                   'console': {
                       # Set the level to "DEBUG" for verbose output logging.