jython-users

[Jython-users] Time Conflict?

[Mike H. <th...@bi...>]

I'm using an Java API that returns a java.util.Date object and I want to
compare that value with the current time.

According to the JDK 1.3 docs, Date.getTime() returns the number of
miliseconds sence January 1, 1970.  Apparently, time.time() in Jython
does not:

>>> time.time()
1.015358378608E9
>>> float(wItems[0].JobStartDate.getTime())
1.015268088E12

Is this a bug?  What is the epoch that Jython uses? Does anyone have a
work-around? 

-- mikeh

Re: [Jython-users] Time Conflict?

[Kevin B. <kb...@ca...>]

Mike Hostetler wrote:

> >>> time.time()
> 1.015358378608E9
> >>> float(wItems[0].JobStartDate.getTime())
> 1.015268088E12

J/Python reports _seconds_ since Jan 1, 1970
Java reports _milliseconds_ since Jan 1, 1970

>>> import time
>>> from java.util import *
>>> Date().getTime() - time.time() * 1000
-47.0
>>> Date().getTime() - time.time() * 1000
0.0
>>> Date().getTime() - time.time() * 1000
0.0
>>> Date().getTime() - time.time() * 1000
0.0
>>> Date().getTime() - time.time() * 1000
0.0
>>> Date().getTime() - time.time() * 1000
0.0
>>> Date().getTime() - time.time() * 1000
0.0

Darn my timing on that first one!

>>> for i in range( 1000 ):
...   if ( Date().getTime() != time.time() * 1000 ): print "woops"
... 
woops
woops
woops
woops
woops
>>>

1/2 of 1 % chance, and I hit different clock ticks. *sigh*

:-)

Actually, it was probably the first call initialization/class loading... 

kb