Zope Version (Zope 2.5.1 (source release, python 2.1, linux2), python 2.1.3, linux2) Python Version 2.1.3 (#1, May 15 2002, 15:52:42) [GCC 2.95.4 20011002 (Debian prerelease) I've got this script which returns strange results: print context.ZopeTime() print context.ZopeTime().toZone('US/East-Indiana') print context.ZopeTime().strftime('%H:%M%p - %m/%d/%Y %Z') print context.ZopeTime().toZone('US/East-Indiana').strftime('%H:%M%p - %m/%d/%Y %Z') return printed The output from this script is: 2002/07/08 16:24:44.687 US/Eastern 2002/07/08 16:24:44.689 US/East-Indiana 17:24PM - 07/08/2002 EST 16:24PM - 07/08/2002 EST The output of the 3rd test case is incorrect. It's as if strftime is changing the time zone. Also the time zone is set to US/East-Indiana in /etc/timezone, yet the default time zone for Zope Time is US/Eastern. We do not want our users to have to manually set the time zone with the toZone method. Any hints? Thanks, -Brian
-> The output of the 3rd test case is incorrect. It's as if strftime is -> changing the time zone. I'd recommend two things: 1) Look at TZ and LC_TIME to see if either is defined in Zope's shell environment 2) Write a super-simple test program in C that utilizes the C version of strftime() and see if your results differ from doing it in Zope. My guess is that doing (2) above will produce the same result, meaning the problem is not within Zope. Good luck. --Derek
participants (2)
-
brian.r.brinegar.1 -
Derek Simkowiak