Raymond Hettinger python at rcn.com
Mon Aug 19 11:44:54 EDT 2002

• Previous message (by thread): Date Conversion problem: Date == 2079/12/31
• Next message (by thread): Date Conversion problem: Date == 2079/12/31
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

"Bradley D. Larson" wrote
>
> Fourth Shift utilizes 2079/12/31 as the "end of time" for items that
> do not expire.  Unfortunately the python "time" lib does not handle
> this date.  I have attempted to convert the date to something else
> in the sql call (eg. to_date(out_date,'YYYYMMDD')) but this does
> not appear to be supported in the Fourth Shift ODBC/DB calls.
>
> Does anyone know if this date is pushed back farther in python 2.2?
>
> Or do you know of a work around...

Hye-Shik Chang wrote a patch to calendar.py that expands the
date range.  See www.python.org/sf/483864


Raymond Hettinger

---

• Previous message (by thread): Date Conversion problem: Date == 2079/12/31
• Next message (by thread): Date Conversion problem: Date == 2079/12/31
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list