The time 2177798400.000000 is beyond the range of this Python implementation.
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 ;-) Bye and thanks!
--- 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 ;-) --- this is the end of the world on 32bits machines (the unix time being the number of milliseconds from jan 01, 1970) and this number is going to overflow by 2038. you have a (lot) of material on the net adressing this issue, go for google... $ven
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
participants (3)
-
Junk -
Sven Hohage -
Tino Wildenhain