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

Mariatta Wijaya added the comment: New changeset 8c851fa3d3044d5bc53e9f931129f5987ece401d by Mariatta in branch '3.5': bpo-29026: Clarify documentation of time.time (GH-34) (GH-418) https://github.com/python/cpython/commit/8c851fa3d3044d5bc53e9f931129f5987ece401d --

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

Mariatta Wijaya added the comment: New changeset b8f5d07158f171a18be4d42f9769d3c9c073e748 by Mariatta in branch '3.6': bpo-29026: Clarify documentation of time.time (GH-34) (GH-417) https://github.com/python/cpython/commit/b8f5d07158f171a18be4d42f9769d3c9c073e748 --

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

STINNER Victor added the comment: Mariatta: "Hi, does this need backport to 2.7? I'm getting a lot of conflicts while trying to do that... Not sure how to proceed." I think it's ok to leave Python 2.7 doc unchanged. It's only a minor doc enhancement, the 2.7 doc is still correct. I close the

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

Mariatta Wijaya added the comment: Hi, does this need backport to 2.7? I'm getting a lot of conflicts while trying to do that... Not sure how to proceed. -- nosy: +Mariatta ___ Python tracker

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

Changes by Mariatta Wijaya : -- pull_requests: +349 ___ Python tracker ___ ___

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

Changes by Mariatta Wijaya : -- pull_requests: +348 ___ Python tracker ___ ___

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

Changes by Ezio Melotti : -- Removed message: http://bugs.python.org/msg288063 ___ Python tracker ___

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

Nick Coghlan added the comment: New changeset 23557d59b819f57800ddef0b1373acef8e024670 by Victor Stinner in branch 'ncoghlan-devguide-link': bpo-29026: Clarify documentation of time.time (#34) https://github.com/python/cpython/commit/23557d59b819f57800ddef0b1373acef8e024670 -- nosy:

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

Changes by Eric Appelt : -- pull_requests: +91 ___ Python tracker ___ ___

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

STINNER Victor added the comment: New changeset 23557d59b819f57800ddef0b1373acef8e024670 by Victor Stinner in branch 'master': bpo-29026: Clarify documentation of time.time (#34) https://github.com/python/cpython/commit/23557d59b819f57800ddef0b1373acef8e024670 --

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

Eric Appelt added the comment: As we have moved to GitHub and mandatory reviews with Pull Requests, I have created a new patch in PR#34 which incorporates Victor's suggestions. -- ___ Python tracker

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

Eric Appelt added the comment: I had some checks performed on a Windows platform using the following snippet: # valid for 2016 import time def check(): t = time.gmtime() print(46*86400*365 + 11*86400 + (t.tm_yday-1)*86400 + t.tm_hour*3600 + t.tm_min*60 + t.tm_sec)

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

STINNER Victor added the comment: Another suggestion: mention localtime() and gmtime() in time() documentation to explain how to convert such timestamp to a more common date format. -- ___ Python tracker

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

Eric Appelt added the comment: I looked at the documentation and implementation and made a patch to hopefully clarify the issue. I also have some comments: - The term "epoch" is actually defined at the top of the page with instructions for how to determine it, i.e. run "gmtime(0)". - I added

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

Eric Appelt added the comment: I would be happy to work on a documentation patch for this - I'll try to have something up by tomorrow evening if no one beats me to it. -- nosy: +Eric Appelt ___ Python tracker

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

STINNER Victor added the comment: > time.time() is not quite UTC on Unix Handling time is a complex task, so we should enhance the doc to help users. If there are multiple cases, we can list them: "time.time() uses UTC timezone with or without leap seconds". Maybe with a link to

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

Marc-Andre Lemburg added the comment: time.time() is not quite UTC on Unix: it usually (*) doesn't include leap seconds, which UTC does. The Wikipedia page has a good definition and explanation: https://en.wikipedia.org/wiki/Unix_time (*) "usually" because POSIX defines time() to not include

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

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.