[Zope] ZopeTime() trouble.

[J. Cameron Cooper]

>Here is the Zope CP info I have...
>
>Linux Box:
>You are running Zope version: Zope 1.10.3 (source release, python 1.5.1,
>linux2), on Python 1.5.2 (#0, Dec 27 2000, 13:59:38) [GCC 2.95.2 20000220
>(Debian GNU/Linux)] on linux2
>
>Win32:
>You are running Zope version: Zope 1.10.3 (binary release, python 1.5.1,
>win32-x86), on Python 1.5.1 (#0, Nov 18 1998, 12:17:58) [MSC 32 bit (Intel)]
>on win32.
>
>Now, would it be possible that this minor difference actually justifies the
>DateTime() problem? (Python 1.5.2 vs. 1.5.1)
>  
>
It's extremely possible. There's a reason 1.5.2 is still The Python 
Version and 1.5.1 isn't. You should try and see if that's the problem.

The other issue is that Python has different time implementations 
between Unix and Windows, since it relies on the OS's c libraries. I 
think I remember that there's no strptime (string parse time) function 
in the Windows C library. I think this is still true, in fact, though 
there are pure-Python implementations now.

http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/56036

I think that current versions of Zope's DateTime use one of these to get 
around this problem, but who knows about the version you have.

One other problem may be Y2K. The Python time module was fixed in 1.5.2 
for Y2K problems.

          --jcc

-- 
"My point and period will be throughly wrought,
Or well or ill, as this day's battle's fought."