Re: [Python-Dev] Holes in time

Since we're on the subject, its always distressed me (in a purely intellectual way) that Unix time doesn't _really_ convert to wall-clock time properly, because it ignores leap seconds. The effect of this is that times in the past get converted incorrectly by several seconds (how many depending on exactly when in the past, of course).

I don't suppose there's interest in fixing that?

Given how timestamps in a typical Unix system are used, I think ignoring leap seconds is the only sensible thing. The POSIX standard agrees. If by "fixing" you mean taking leap seconds into account in any way, I would strongly object that. --Guido van Rossum (home page: http://www.python.org/~guido/)