[3.12] gh-85453: Make numeric literals consistent across datetime.rst (GH-118245...

Remove code formatting from remaining numeric literals.
(cherry picked from commit 59a4d52973ca73bd739f914e88243a31dbef6b32)

Co-authored-by: edson duarte <eduarte.uatach@gmail.com>

diff --git a/Doc/library/datetime.rst b/Doc/library/datetime.rst
index 13151e5c479d3af10fd05947d43182531595c0a4..c7545db2f241a6e751285ee16c248ad95291b398 100644 (file)
--- a/Doc/library/datetime.rst
+++ b/Doc/library/datetime.rst
@@ -91,7 +91,7 @@ The :mod:`!datetime` module exports the following constants:
 .. data:: MAXYEAR
 
    The largest year number allowed in a :class:`date` or :class:`.datetime` object.
-   :const:`MAXYEAR` is ``9999``.
+   :const:`MAXYEAR` is 9999.
 
 .. attribute:: UTC
 
@@ -2514,7 +2514,7 @@ information, which are supported in ``datetime.strptime`` but are discarded by
 
 For :class:`.time` objects, the format codes for year, month, and day should not
 be used, as :class:`!time` objects have no such values. If they're used anyway,
-``1900`` is substituted for the year, and 1 for the month and day.
+1900 is substituted for the year, and 1 for the month and day.
 
 For :class:`date` objects, the format codes for hours, minutes, seconds, and
 microseconds should not be used, as :class:`date` objects have no such
@@ -2642,4 +2642,4 @@ Notes:
        <https://web.archive.org/web/20220531051136/https://webspace.science.uu.nl/~gent0113/calendar/isocalendar.htm>`_
        for a good explanation.
 
-.. [#] Passing ``datetime.strptime('Feb 29', '%b %d')`` will fail since ``1900`` is not a leap year.
+.. [#] Passing ``datetime.strptime('Feb 29', '%b %d')`` will fail since 1900 is not a leap year.