@@ -761,7 +761,7 @@ printed on the console; on the server side, you should see something like:
761
761
762
762
Note that there are some security issues with pickle in some scenarios. If
763
763
these affect you, you can use an alternative serialization scheme by overriding
764
- the :meth: `~handlers. SocketHandler.makePickle ` method and implementing your
764
+ the :meth: `~SocketHandler.makePickle ` method and implementing your
765
765
alternative there, as well as adapting the above script to use your alternative
766
766
serialization.
767
767
@@ -835,6 +835,8 @@ To test these files, do the following in a POSIX environment:
835
835
You may need to tweak the configuration files in the unlikely event that the
836
836
configured ports clash with something else in your test environment.
837
837
838
+ .. currentmodule :: logging
839
+
838
840
.. _context-info :
839
841
840
842
Adding contextual information to your logging output
@@ -1546,7 +1548,7 @@ Sometimes you want to let a log file grow to a certain size, then open a new
1546
1548
file and log to that. You may want to keep a certain number of these files, and
1547
1549
when that many files have been created, rotate the files so that the number of
1548
1550
files and the size of the files both remain bounded. For this usage pattern, the
1549
- logging package provides a :class: `~handlers. RotatingFileHandler `::
1551
+ logging package provides a :class: `RotatingFileHandler `::
1550
1552
1551
1553
import glob
1552
1554
import logging
@@ -1594,6 +1596,8 @@ and each time it reaches the size limit it is renamed with the suffix
1594
1596
Obviously this example sets the log length much too small as an extreme
1595
1597
example. You would want to set *maxBytes * to an appropriate value.
1596
1598
1599
+ .. currentmodule :: logging
1600
+
1597
1601
.. _format-styles :
1598
1602
1599
1603
Use of alternative formatting styles
@@ -1840,6 +1844,7 @@ However, it should be borne in mind that each link in the chain adds run-time
1840
1844
overhead to all logging operations, and the technique should only be used when
1841
1845
the use of a :class: `Filter ` does not provide the desired result.
1842
1846
1847
+ .. currentmodule :: logging.handlers
1843
1848
1844
1849
.. _zeromq-handlers :
1845
1850
@@ -1917,6 +1922,8 @@ of queues, for example a ZeroMQ 'subscribe' socket. Here's an example::
1917
1922
:ref: `A more advanced logging tutorial <logging-advanced-tutorial >`
1918
1923
1919
1924
1925
+ .. currentmodule :: logging
1926
+
1920
1927
An example dictionary-based configuration
1921
1928
-----------------------------------------
1922
1929
@@ -3918,8 +3925,8 @@ that in other languages such as Java and C#, loggers are often static class
3918
3925
attributes. However, this pattern doesn't make sense in Python, where the
3919
3926
module (and not the class) is the unit of software decomposition.
3920
3927
3921
- Adding handlers other than :class: `NullHandler ` to a logger in a library
3922
- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3928
+ Adding handlers other than :class: `~logging. NullHandler ` to a logger in a library
3929
+ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3923
3930
3924
3931
Configuring logging by adding handlers, formatters and filters is the
3925
3932
responsibility of the application developer, not the library developer. If you
0 commit comments