Aahz Maruch aahz at panix.com
Tue Oct 3 01:18:22 EDT 2000

• Previous message (by thread): range of mktime
• Next message (by thread): range of mktime
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

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.
-- 
                      --- Aahz (Copyright 2000 by aahz at pobox.com)

Androgynous poly kinky vanilla queer het    <*>     http://www.rahul.net/aahz/
Hugs and backrubs -- I break Rule 6

There may or may not be a smiley above.  --Aahz

---

• Previous message (by thread): range of mktime
• Next message (by thread): range of mktime
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list