https://github.com/python/cpython/commit/59a4d52973ca73bd739f914e88243a31dbef6b32
commit: 59a4d52973ca73bd739f914e88243a31dbef6b32
branch: main
author: edson duarte <[email protected]>
committer: erlend-aasland <[email protected]>
date: 2024-04-24T20:19:54Z
summary:

gh-85453: Make numeric literals consistent across datetime.rst (#118245)

Remove code formatting from remaining numeric literals.

files:
M Doc/library/datetime.rst

diff --git a/Doc/library/datetime.rst b/Doc/library/datetime.rst
index 84fede472eeacc..b1b5e04c74b066 100644
--- 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
 
@@ -2561,7 +2561,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
@@ -2708,4 +2708,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.

_______________________________________________
Python-checkins mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-checkins.python.org/
Member address: [email protected]

Reply via email to