25 May
2001
25 May
'01
7:46 p.m.
Hi, --On Freitag, 25. Mai 2001 12:30 +0200 Sven Hohage <sven.hohage@zeitspringer.de> wrote:
Hello, i've got this problem with the date-value 2039/01/05. Nearby this value it seems to be a python-time-limit! Is this changed with 2.0 and when not what can you do?? Tell your customer not to think about the future ;-)
Where is the problem? Where is the limit? AFAIK zopes DateTime object uses a floating point number internally to store the seconds. I dont see this overflow in the near future :) However, I can instantiate even DateTime('2052/01/05') May be you have mixed it up with the systemclock - c-library interface which is in fact 32bit only (on most systems)? Regards Tino