This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients belopolsky, docs@python, vstinner
Date 2016-12-20.14:24:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1482243889.09.0.538886851254.issue29026@psf.upfronthosting.co.za>
In-reply-to
Content
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
History
Date User Action Args
2016-12-20 14:24:49vstinnersetrecipients: + vstinner, belopolsky, docs@python
2016-12-20 14:24:49vstinnersetmessageid: <1482243889.09.0.538886851254.issue29026@psf.upfronthosting.co.za>
2016-12-20 14:24:49vstinnerlinkissue29026 messages
2016-12-20 14:24:48vstinnercreate