Commit c1f079f3 authored by Gregory P. Smith's avatar Gregory P. Smith

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

parent b0ae0ac6
...@@ -87,6 +87,11 @@ instantiated directly, but always through the module-level function ...@@ -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 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. 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) .. method:: Logger.isEnabledFor(lvl)
...@@ -319,6 +324,11 @@ subclasses. However, the :meth:`__init__` method in subclasses needs to call ...@@ -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 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). 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) .. method:: Handler.setFormatter(form)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment