Tim Peters tim.one at comcast.net
Mon Jul 22 22:16:31 EDT 2002

• Previous message (by thread): calendar lameness!
• Next message (by thread): calendar lameness!
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

[Terry Hancock]
> ...
> "calendar" is pretty neat -- except it has pretty
> annoying arbitrary limits on the date:
>
> 1900-1/1 to 2038-1/18
>
> I can see that this is adequate for a business
> planner, but for historical or astronomical uses,
> it's really inadequate.
> ...

Get Marc-Andre Lemburg's mxDateTime.  Python 2.3 will have some sort of
standard more-powerful datetime gimmick, but Guido is anti-interested in
arguing with datetime weenies <0.9 wink>.

> ...
> This is Python 2.1. Anyway -- any chance these got
> fixed in a later release?

None.

> Why the range?
> ...
> Actually, it looks like maybe it's "mktime" that
> is the limiter here (?).

Bingo!

> ...
> It seems like Python longs would make it unnecessary to
> have such arbitrary limits.

See Demo/classes/Dates.py in the Python source distribution.

---

• Previous message (by thread): calendar lameness!
• Next message (by thread): calendar lameness!
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list