summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>2023-01-20 05:06:04 (GMT)
committerGitHub <noreply@github.com>2023-01-20 05:06:04 (GMT)
commit10c61301240374701279aa8f87bf9f1caf1e9c9a (patch)
tree32883fa7697cd32069ccffe3a9a168a459be1dd6
parent2c1eeb508cf202d744d06b7d76d002d76f7f45bf (diff)
downloadcpython-10c61301240374701279aa8f87bf9f1caf1e9c9a.zip
cpython-10c61301240374701279aa8f87bf9f1caf1e9c9a.tar.gz
cpython-10c61301240374701279aa8f87bf9f1caf1e9c9a.tar.bz2
gh-101041: Fix a misspelled name of `utctimetuple` in a doc warning (GH-101042)
(cherry picked from commit 8e9d08b062bbabfe439bc73f82e3d7bb3800189e) Co-authored-by: Oleg Iarygin <oleg@arhadthedev.net>
-rw-r--r--Doc/library/datetime.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/library/datetime.rst b/Doc/library/datetime.rst
index f222ec9..e23d2a9 100644
--- a/Doc/library/datetime.rst
+++ b/Doc/library/datetime.rst
@@ -1342,7 +1342,7 @@ Instance methods:
Because naive ``datetime`` objects are treated by many ``datetime`` methods
as local times, it is preferred to use aware datetimes to represent times
- in UTC; as a result, using ``utcfromtimetuple`` may give misleading
+ in UTC; as a result, using :meth:`datetime.utctimetuple` may give misleading
results. If you have a naive ``datetime`` representing UTC, use
``datetime.replace(tzinfo=timezone.utc)`` to make it aware, at which point
you can use :meth:`.datetime.timetuple`.