Re: [Zope] Weird interaction between int() and DateTime.timeTime

On Thu, 25 May 2000, Chris Withers wrote: > "Jeff K. Hoffman" wrote: > > Python 1.5.2 (#3, Mar 8 2000, 16:34:52) [C] on sunos5 > > Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam > > >>> > > >>> f = 1. > > >>> f > > 2.0 > > >>> int(f) > > 1 > > >>> >

Re: [Zope] Weird interaction between int() and DateTime.timeTime

[EMAIL PROTECTED] wrote: > >From the python int doc string: > > >>> print int.__doc__ > int(x) -> integer > > Convert a string or number to an integer, if possible. > A floating point argument will be truncated towards zero. I _always_ get bitten by this :( Sorry for my igorance, Chris

Re: [Zope] Weird interaction between int() and DateTime.timeTime

On Thu, May 25, 2000 at 07:44:44PM +0200, [EMAIL PROTECTED] wrote: > > int() works fine (truncating everything behind "."): > > >>> t.timeTime() == 953146937.0 > 0 > >>> t.timeTime() - 953146937.0 > -4.76837158203e-07 > >>> int (round (t.timeTime())) > 953146937

Re: [Zope] Weird interaction between int() and DateTime.timeTime

On Thu, May 25, 2000 at 06:48:51PM +0100, Chris Withers wrote: > "Jeff K. Hoffman" wrote: > > Python 1.5.2 (#3, Mar 8 2000, 16:34:52) [C] on sunos5 > > Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam > > >>> > > >>> f = 1. > > >>> f > > 2.0 > > >>> int(f) >

Re: [Zope] Weird interaction between int() and DateTime.timeTime

[EMAIL PROTECTED] writes: > >>> t.timeTime() > 953146937.0 > >>> int( t.timeTime() ) > 953146936 < This is wrong > >>> int( 953146937.0 ) > 953146937 > > Any ideas on how this can be happening. Stepping through the DateTime module > yields the sensible return valu

Re: [Zope] Weird interaction between int() and DateTime.timeTime

"Jeff K. Hoffman" wrote: > Python 1.5.2 (#3, Mar 8 2000, 16:34:52) [C] on sunos5 > Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam > >>> > >>> f = 1. > >>> f > 2.0 > >>> int(f) > 1 > >>> > the int() function takes a different code path and returns 1, c

Re: [Zope] Weird interaction between int() and DateTime.timeTime

On Thu, 25 May 2000 [EMAIL PROTECTED] wrote: > 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

Re: [Zope] Weird interaction between int() and DateTime.timeTime

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. And will be in 2.2? Chris ___ Zope maill

Re: [Zope] Weird interaction between int() and DateTime.timeTime

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

Re: [Zope] Weird interaction between int() and DateTime.timeTime

[EMAIL PROTECTED] wrote: > > In a previous posting about Netscape Image problems I mentioned a weird > interaction between int() and DateTime.timeTime(). I can reproduce the error > within the python interpreter as follows- > > Python 1.5.2 (#5, Jan 6 2000, 17:10:24) [GCC egcs-2.91.66 19990314

[Zope] Weird interaction between int() and DateTime.timeTime

In a previous posting about Netscape Image problems I mentioned a weird interaction between int() and DateTime.timeTime(). I can reproduce the error within the python interpreter as follows- Python 1.5.2 (#5, Jan 6 2000, 17:10:24) [GCC egcs-2.91.66 19990314/Linux (egcs- on linux2 Copyright 1991