[issue4775] Incorrect documentation - UTC time

Marc-Andre Lemburg report at bugs.python.org
Thu Jan 1 22:39:52 CET 2009


Marc-Andre Lemburg <mal at egenix.com> added the comment:

FWIW: POSIX defines Unix time_t *not* to include leap seconds.

You can easily check whether your platform or C lib behaves
POSIX-ly correct or not:

   POSIX: 1986-12-31 23:59:59 UTC == 536457599 ticks

   With leap seconds:		  == 536457612 ticks

   (since there were 13 leap seconds in the years 1972-1985)

For most practical purposes the difference doesn't really matter,
since date differences are usually counted in days, not seconds.

In cases where it does matter, you're better off with a custom
solution, since applications or other libraries tend not to handle
leap seconds well.

----------
nosy: +lemburg

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue4775>
_______________________________________


More information about the Python-bugs-list mailing list