[docs] [issue29026] time.time() documentation should mention UTC timezone
report at bugs.python.org
Tue Dec 20 09:24:49 EST 2016
New submission from STINNER Victor:
The documentation of the time.time() mentions "epoch" which it doesn't define epoch. If I recall correctly, it's January 1st, 1970 on most OS and most implementations of Python, except of IronPython which uses a different epoch.
Moreover, the timezone is not defined. In practice, it's UTC, so it would be nice to document it.
I opened this issue because I wasn't sure if time.time() is impacted by DST or not. The answer is no. Maybe the behaviour of time.time() on DST should also be documentation. Hint: it is not impacted by DST since it uses UTC timezone.
Related question on StackOverflow:
assignee: docs at python
nosy: belopolsky, docs at python, haypo
title: time.time() documentation should mention UTC timezone
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7
Python tracker <report at bugs.python.org>
More information about the docs