[issue43869] Fix documentation of epoch/time.time

Change by STINNER Victor : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue43869] Fix documentation of epoch/time.time

STINNER Victor added the comment: New changeset a847785b40ed8819bde2dac5849dc31d15e99a74 by Victor Stinner in branch 'main': bpo-43869: Time Epoch is the same on all platforms (GH-30664) https://github.com/python/cpython/commit/a847785b40ed8819bde2dac5849dc31d15e99a74 --

[issue43869] Fix documentation of epoch/time.time

Change by Irit Katriel : -- versions: +Python 3.11 -Python 3.10, Python 3.6, Python 3.7, Python 3.8, Python 3.9 ___ Python tracker ___

[issue43869] Fix documentation of epoch/time.time

STINNER Victor added the comment: I was going to close the change, but I had a last look and... oh... I found that the Python test suite checks that the Epoch is 1970-01-01 at 00:00 since 2008! I wrote GH-30664 to add an explicit test and I updated the doc. --

[issue43869] Fix documentation of epoch/time.time

Change by STINNER Victor : -- pull_requests: +28865 pull_request: https://github.com/python/cpython/pull/30664 ___ Python tracker ___

[issue43869] Fix documentation of epoch/time.time

STINNER Victor added the comment: New changeset ff7703c4b609a697ada8165fd1c52a73404b6d07 by Miguel Brito in branch 'main': bpo-43869: Improve epoch docs (GH-25777) https://github.com/python/cpython/commit/ff7703c4b609a697ada8165fd1c52a73404b6d07 --

[issue43869] Fix documentation of epoch/time.time

Miguel Brito added the comment: Seen that no one is working on this issue I created an PR to clarify the docs. https://github.com/python/cpython/pull/25777 -- ___ Python tracker

[issue43869] Fix documentation of epoch/time.time

Change by Miguel Brito : -- keywords: +patch nosy: +miguendes nosy_count: 4.0 -> 5.0 pull_requests: +24467 stage: -> patch review pull_request: https://github.com/python/cpython/pull/25777 ___ Python tracker

[issue43869] Fix documentation of epoch/time.time

STINNER Victor added the comment: "platform dependent" was added in 2017 by the commit (bpo-29026): commit 23557d59b819f57800ddef0b1373acef8e024670 Author: Eric Appelt Date: Thu Feb 16 05:00:45 2017 -0500 bpo-29026: Clarify documentation of time.time (#34) * bpo-29026:

[issue43869] Fix documentation of epoch/time.time

STINNER Victor added the comment: time.time doc says "On Windows and most Unix systems, the epoch is January 1, 1970, 00:00:00 (UTC)" The epoch doc says "For Unix, the epoch is January 1, 1970, 00:00:00 (UTC)". At least, the epoch doc can be completed to also mention that it's the same on

[issue43869] Fix documentation of epoch/time.time

STINNER Victor added the comment: On Windows 10 (build 20H2), I get: Python 3.10.0a7+ (heads/master:b136b1aac4, Apr 16 2021, 14:36:39) [MSC v.1928 64 bit (AMD64)] on win32 >>> import time >>> time.gmtime(0) time.struct_time(tm_year=1970, tm_mon=1, tm_mday=1, tm_hour=0, tm_min=0, tm_sec=0,

[issue43869] Fix documentation of epoch/time.time

New submission from Ofek Lev : The descriptions for the following: - https://docs.python.org/3/library/time.html#epoch - https://docs.python.org/3/library/time.html#time.time indicate that it is platform dependent. However, that is likely untrue. See the brief discussion here: