From c6646c097aceec4b4ee64968e875b508e908e9f4 Mon Sep 17 00:00:00 2001
From: Vinay Sajip <vinay_sajip@yahoo.co.uk>
Date: Wed, 22 Sep 2004 12:55:16 +0000
Subject: [PATCH] Added getLoggerClass()

---
 Doc/lib/liblogging.tex | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/Doc/lib/liblogging.tex b/Doc/lib/liblogging.tex
index ecb3791dfb8..cfbb8384f10 100644
--- a/Doc/lib/liblogging.tex
+++ b/Doc/lib/liblogging.tex
@@ -144,6 +144,19 @@ This means that logger instances never need to be passed between different
 parts of an application.
 \end{funcdesc}
 
+\begin{funcdesc}{getLoggerClass}{}
+Return either the standard \class{Logger} class, or the last class passed to
+\function{setLoggerClass()}. This function may be called from within a new
+class definition, to ensure that installing a customised \class{Logger} class
+will not undo customisations already applied by other code. For example:
+
+\begin{verbatim}
+ class MyLogger(logging.getLoggerClass()):
+     # ... override behaviour here
+\end{verbatim}
+
+\end{funcdesc}
+
 \begin{funcdesc}{debug}{msg\optional{, *args\optional{, **kwargs}}}
 Logs a message with level \constant{DEBUG} on the root logger.
 The \var{msg} is the message format string, and the \var{args} are the