mktime() like function to produce GMT?
Mark Nottingham
mnot at pobox.com
Tue May 4 18:19:40 EDT 1999
> "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.
Actually, it's best if it doesn't, unless leap seconds are accouted for
throughout all time-centric functions (not a small job, from what I gather).
Otherwise, parsing and printing a date (as I'm doing) will change it, for
instance.
Thanks, M.A, Fredrik and Guido!
More information about the Python-list
mailing list