Message78497
There is a systemic error in the Python documentation on time (such as
<http://docs.python.org/library/time.html>). The term UTC is used
incorrectly in the documentation where the term UT1 should be used.
The difference is that UTC includes leap seconds, whereas UT1 does not (see <http://en.wikipedia.org/wiki/Coordinated_Universal_Time>). The
conversion routines ignore leap seconds, e.g., (time.mktime((2000,1,1,12,0,0,0,0,0))-
time.mktime((1990,1,1,12,0,0,0,0,0))) returns an exact multiple of
24*60*60 and does not include all the leap seconds added between those
dates. Using UT1 is more sensible that using UTC, since with UTC it is
impossible to know when future leap seconds will be added, and hence
impossible to convert future times to a number of seconds past the
epoch. |
|
Date |
User |
Action |
Args |
2008-12-30 02:17:22 | luckmor | set | recipients:
+ luckmor, georg.brandl |
2008-12-30 02:17:22 | luckmor | set | messageid: <1230603442.34.0.985593856271.issue4775@psf.upfronthosting.co.za> |
2008-12-30 02:17:21 | luckmor | link | issue4775 messages |
2008-12-30 02:17:19 | luckmor | create | |
|