range of mktime

Bob van der Poel bvdpoel at uniserve.com
Tue Oct 3 11:52:51 EDT 2000


Aahz Maruch wrote:
> 
> In article <39D923A6.8A0A74B8 at uniserve.com>,
> bob van der Poel  <bvdpoel at uniserve.com> 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?
> 
> That surprises me mildly; the usual range is 1970 to 2038 (matching the
> range of the Unix 32-bit clock).  You may want to use mxDateTime instead
> for greater range, precision, and utility.

Thx for the pointer to mxDateTime. Found and dl'd it, looks very neat.
I'll try using it later.

-- 
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bvdpoel at uniserve.com
WWW:   http://users.uniserve.com/~bvdpoel




More information about the Python-list mailing list