Mention the additional way to use the lvl parameter and when it changed.

diff --git a/Doc/library/logging.rst b/Doc/library/logging.rst
index df5e5a5aeadfb3b8036ebe0295a750f25815ee24..5a4116053a2701d43458fb051b1dc3aab4fb1a8c 100644 (file)
--- a/Doc/library/logging.rst
+++ b/Doc/library/logging.rst
@@ -87,6 +87,11 @@ instantiated directly, but always through the module-level function
    If the root is reached, and it has a level of NOTSET, then all messages will be
    processed. Otherwise, the root's level will be used as the effective level.
 
+   .. versionchanged:: 3.2
+      The *lvl* parameter now accepts a string representation of the
+      level such as 'INFO' as an alternative to the integer constants
+      such as :const:`INFO`.
+
 
 .. method:: Logger.isEnabledFor(lvl)
 
@@ -319,6 +324,11 @@ subclasses. However, the :meth:`__init__` method in subclasses needs to call
    severe than *lvl* will be ignored. When a handler is created, the level is set
    to :const:`NOTSET` (which causes all messages to be processed).
 
+   .. versionchanged:: 3.2
+      The *lvl* parameter now accepts a string representation of the
+      level such as 'INFO' as an alternative to the integer constants
+      such as :const:`INFO`.
+
 
 .. method:: Handler.setFormatter(form)