From: guido at eric.cnri.reston.va.us (Guido van Rossum)
Date: 04 May 1999 10:56:13 -0400
Subject: mktime() like function to produce GMT?
References: <00be01be9308$c649cf60$0301a8c0@cbd.net.au> <3729B855.3A7C6B5A@lemburg.com> <5lu2ty9lpx.fsf@eric.cnri.reston.va.us> <372D60B3.58DE3818@lemburg.com> <003d01be954d$f22230e0$0301a8c0@cbd.net.au> <372D9DAC.2BD7C604@lemburg.com> <5laevm9doj.fsf@eric.cnri.reston.va.us> <372EB855.DF47D72@lemburg.com> <372EB98F.58F9931@lemburg.com>
Message-ID: <5l7lqoanoy.fsf@eric.cnri.reston.va.us>
X-UID: 1724                                                

"M.-A. Lemburg" <mal at lemburg.com> writes:
> The last short sentence pretty nicely covers up the problems with timegm()
> :-) "POSIX algorithm" means that leap seconds are not accounted for.

And what's wrong with that?  The Unix time is just as much an
*encoding* of time values as any other.  Few clocks in the world are
accurate enough to care about leap seconds.  The rest of us
occasionally synchronize with a master clock.  I don't care about leap 
seconds and never will.

--Guido van Rossum (home page: http://www.python.org/~guido/)




