Re: os.clock conversion to milliseconds under MacOS X

[Joseph Wallace <tangent128@...>]

On 12/17/2014 02:52 PM, Isaac Dupree wrote:
> 
> That documentation cannot be correct on Unix-time systems if there is a
> leap second between t1 and t2.
> 
> (For example, in UTC Unix time, 1341144000 - 1341057600 = 86400 but
> there were actually 86401 seconds from June 30, 2012 12:00:00 UTC to
> July 1, 2012 12:00:00 UTC.  That said, even Python's documentation
> doesn't clearly tell me whether its time deltas treat leap seconds as
> being zero seconds long; we seem to be resigned to IERS-initiated
> software bugs every few years.)
> 

Depends if you are using UTC Unix time (traditional) or TAI Unix time
(the "right/" tzdata files). ;)