Message283690
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 |
|
Date |
User |
Action |
Args |
2016-12-20 14:24:49 | vstinner | set | recipients:
+ vstinner, belopolsky, docs@python |
2016-12-20 14:24:49 | vstinner | set | messageid: <1482243889.09.0.538886851254.issue29026@psf.upfronthosting.co.za> |
2016-12-20 14:24:49 | vstinner | link | issue29026 messages |
2016-12-20 14:24:48 | vstinner | create | |
|