[docs] [issue29026] time.time() documentation should mention UTC timezone

STINNER Victor 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.

https://docs.python.org/dev/library/time.html#time.time

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:
http://stackoverflow.com/questions/32469318/python-time-time-and-daylight-saving-time

----------
assignee: docs at python
components: Documentation
messages: 283690
nosy: belopolsky, docs at python, haypo
priority: normal
severity: normal
status: open
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>
<http://bugs.python.org/issue29026>
_______________________________________


More information about the docs mailing list