bob van der Poel wrote: > > Using time.mktime() it appears that on my linux box the valid range is > 1902...2038. Is this platform consistent, or, if not, is there a way to > determine at runtime the valid range? Would reading the value in a loop until it wraps around be too much of a problem? :)