@@ -1001,13 +1001,13 @@ datetime and time
10011001 after 1900. The new supported year range is from 1000 to 9999 inclusive.
10021002
10031003* Whenever a two-digit year is used in a time tuple, the interpretation has been
1004- governed by :attr: `time.accept2dyear `. The default is * True * which means that
1004+ governed by :attr: `time.accept2dyear `. The default is `` True `` which means that
10051005 for a two-digit year, the century is guessed according to the POSIX rules
10061006 governing the ``%y `` strptime format.
10071007
10081008 Starting with Py3.2, use of the century guessing heuristic will emit a
10091009 :exc: `DeprecationWarning `. Instead, it is recommended that
1010- :attr: `time.accept2dyear ` be set to * False * so that large date ranges
1010+ :attr: `time.accept2dyear ` be set to `` False `` so that large date ranges
10111011 can be used without guesswork::
10121012
10131013 >>> import time, warnings
@@ -1043,7 +1043,7 @@ The :mod:`math` module has been updated with six new functions inspired by the
10431043C99 standard.
10441044
10451045The :func: `~math.isfinite ` function provides a reliable and fast way to detect
1046- special values. It returns * True * for regular numbers and * False * for *Nan * or
1046+ special values. It returns `` True `` for regular numbers and `` False `` for *Nan * or
10471047*Infinity *:
10481048
10491049>>> from math import isfinite
@@ -1193,7 +1193,7 @@ exception or silently drop the event depending on the value of
11931193
11941194The use of filters has been simplified. Instead of creating a
11951195:class: `~logging.Filter ` object, the predicate can be any Python callable that
1196- returns * True * or * False * .
1196+ returns `` True `` or `` False `` .
11971197
11981198There were a number of other improvements that add flexibility and simplify
11991199configuration. See the module documentation for a full listing of changes in
0 commit comments