https://github.com/python/cpython/commit/3dd3b301b6f6a9a18cfa07d965da15c4908b90dd
commit: 3dd3b301b6f6a9a18cfa07d965da15c4908b90dd
branch: 3.11
author: Serhiy Storchaka <[email protected]>
committer: serhiy-storchaka <[email protected]>
date: 2024-01-29T16:59:59Z
summary:

[3.11] Fix more references to datetime and time classes (GH-114717) (GH-114726)

They could be confused with references to datetime and time modules.
(cherry picked from commit 39c766b579cabc71a4a50773d299d4350221a70b)

files:
M Doc/library/datetime.rst
M Doc/library/mailbox.rst
M Doc/whatsnew/3.8.rst

diff --git a/Doc/library/datetime.rst b/Doc/library/datetime.rst
index d97fa096730ec8..755f937f78a325 100644
--- a/Doc/library/datetime.rst
+++ b/Doc/library/datetime.rst
@@ -1664,7 +1664,7 @@ Usage of ``KabulTz`` from above::
 :class:`.time` Objects
 ----------------------
 
-A :class:`time` object represents a (local) time of day, independent of any 
particular
+A :class:`.time` object represents a (local) time of day, independent of any 
particular
 day, and subject to adjustment via a :class:`tzinfo` object.
 
 .. class:: time(hour=0, minute=0, second=0, microsecond=0, tzinfo=None, *, 
fold=0)
@@ -2497,7 +2497,7 @@ information, which are supported in ``datetime.strptime`` 
but are discarded by
 ``time.strptime``.
 
 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,
+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.
 
 For :class:`date` objects, the format codes for hours, minutes, seconds, and
diff --git a/Doc/library/mailbox.rst b/Doc/library/mailbox.rst
index fab88bfc7e165a..9e737cd5ee449e 100644
--- a/Doc/library/mailbox.rst
+++ b/Doc/library/mailbox.rst
@@ -1027,8 +1027,8 @@ When a :class:`!MaildirMessage` instance is created based 
upon a
       leading "From " or trailing newline. For convenience, *time_* may be
       specified and will be formatted appropriately and appended to *from_*. If
       *time_* is specified, it should be a :class:`time.struct_time` instance, 
a
-      tuple suitable for passing to :meth:`time.strftime`, or ``True`` (to use
-      :meth:`time.gmtime`).
+      tuple suitable for passing to :func:`time.strftime`, or ``True`` (to use
+      :func:`time.gmtime`).
 
 
    .. method:: get_flags()
@@ -1399,8 +1399,8 @@ When a :class:`!BabylMessage` instance is created based 
upon an
       leading "From " or trailing newline. For convenience, *time_* may be
       specified and will be formatted appropriately and appended to *from_*. If
       *time_* is specified, it should be a :class:`time.struct_time` instance, 
a
-      tuple suitable for passing to :meth:`time.strftime`, or ``True`` (to use
-      :meth:`time.gmtime`).
+      tuple suitable for passing to :func:`time.strftime`, or ``True`` (to use
+      :func:`time.gmtime`).
 
 
    .. method:: get_flags()
diff --git a/Doc/whatsnew/3.8.rst b/Doc/whatsnew/3.8.rst
index 4515010635fe08..b140e3bc6c5efa 100644
--- a/Doc/whatsnew/3.8.rst
+++ b/Doc/whatsnew/3.8.rst
@@ -754,8 +754,8 @@ datetime
 --------
 
 Added new alternate constructors :meth:`datetime.date.fromisocalendar` and
-:meth:`datetime.datetime.fromisocalendar`, which construct :class:`date` and
-:class:`datetime` objects respectively from ISO year, week number, and weekday;
+:meth:`datetime.datetime.fromisocalendar`, which construct 
:class:`~datetime.date` and
+:class:`~datetime.datetime` objects respectively from ISO year, week number, 
and weekday;
 these are the inverse of each class's ``isocalendar`` method.
 (Contributed by Paul Ganssle in :issue:`36004`.)
 

_______________________________________________
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