Time (was: Character set wars (was: In defense of Google))

[Christopher Schmidt]

On Tue, Jan 31, 2006 at 05:08:32PM -0500, Tom Buskey wrote:
> On 1/31/06, Fred <puissante at lrc.puissante.com> wrote:
> 
> > What will be interesting to see, and most of us will be around when it
> > happens, is the time the Unix clocks run to an end in 2038. I would like
> > to
> > think by then all timers will be 64-bit (or similar), but you'll never
> > know
> > for sure.
> >
> 
> Windows uses the same clock.  Macintosh used to use a different one, but
> MacOSX is partly FreeBSD based and may have switched.

http://maul.deepsky.com/%7Emerovech/2038.python.txt

Mon Jan 18 22:14:06 2038
Mon Jan 18 22:14:07 2038
Mon Jan 18 22:14:07 2038
Mon Jan 18 22:14:07 2038
Mon Jan 18 22:14:07 2038

(OS X)

Mon Jan 18 22:14:06 2038
Mon Jan 18 22:14:07 2038
Traceback (most recent call last):
  File "2038.python.txt", line 8, in ?
    print time.ctime(t)
ValueError: timestamp out of range for platform time_t

(Debian, Ubuntu)

Note that "30 years in the future" is no longer so far away... at least,
not if you're working with mortgages.

-- 
Christopher Schmidt
Web Developer