From 34599767b8ec58d53243c7d34c6a6b97059eb097 Mon Sep 17 00:00:00 2001 From: lit Date: Fri, 19 Apr 2024 19:28:46 +0800 Subject: [PATCH] gh-88035: update doc-string of `epoch` in timemodule.c (GH-118076) Follow GH-88035, update doc-string of epoch in timemodule.c The epoch is `January 1st, 1970 on all platforms`, according to current documentation. (cherry picked from commit 7c6cc00211772cc2afe0bc5e996b6d28f925d133) Co-authored-by: lit --- Modules/timemodule.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Modules/timemodule.c b/Modules/timemodule.c index 3b46deacdf2de2..126eebc0442d40 100644 --- a/Modules/timemodule.c +++ b/Modules/timemodule.c @@ -1907,8 +1907,8 @@ PyDoc_STRVAR(module_doc, There are two standard representations of time. One is the number\n\ of seconds since the Epoch, in UTC (a.k.a. GMT). It may be an integer\n\ or a floating point number (to represent fractions of seconds).\n\ -The Epoch is system-defined; on Unix, it is generally January 1st, 1970.\n\ -The actual value can be retrieved by calling gmtime(0).\n\ +The epoch is the point where the time starts, the return value of time.gmtime(0).\n\ +It is January 1, 1970, 00:00:00 (UTC) on all platforms.\n\ \n\ The other representation is a tuple of 9 integers giving local time.\n\ The tuple items are:\n\