On Thu, May 25, 2000 at 12:56:48PM -0400, Shane Hathaway wrote:
>
> Simple: DateTime has been using floating-point calculations.  I believe
> all of that has been corrected, however, with the new DateTime module,
> available in the public CVS repository.
> 
> Shane
> 

I don't understand how your answer explains the buggy behaviour. If
DateTime.timeTime() returns a float that's okay. Why should a call to it
wrapped with int() return the incorrect answer?

>> t.timeTime() 
953146937.0 
>> int( t.timeTime() ) 
953146936
>> int( 953146937.0 ) 
953146937

------------------------------------------------------
Andres Corrada-Emmanuel   Email: [EMAIL PROTECTED]
------------------------------------------------------

_______________________________________________
Zope maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope-dev )

Reply via email to