zope server versions and Zopetime() function.
Hello all, I was testing zopetime() function on 2 diffrent versions of zope servers, both running on different linux machines and i was getting 2 diffrent results: <dtml-var expr="ZopeTime().toZone('GMT+1').strftime('%d%m%Y %H:%M:%S - %Z')"> On (Zope 2.6.1 (binary release, python 2.1, linux2-x86), python 2.1.3, linux2) the result was : 28052005 12:15:11 - PST which the correct time in GMT+1 While on (Zope 2.7.6-final, python 2.3.5, linux2) the same code was showing : 28052005 03:56:07 - PDT This is not the correct time in GMT+1, but the current time on the server. What should have gone wrong and how do I solve this. Thanks. KAMAL. Internal Virus Database is out-of-date. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.7.4 - Release Date: 3/18/2005
Hamzat Kamal wrote at 2005-5-28 12:35 +0100:
... I was testing zopetime() function on 2 diffrent versions of zope servers, both running on different linux machines and i was getting 2 diffrent results:
<dtml-var expr="ZopeTime().toZone('GMT+1').strftime('%d%m%Y %H:%M:%S - %Z')">
On (Zope 2.6.1 (binary release, python 2.1, linux2-x86), python 2.1.3, linux2)
the result was : 28052005 12:15:11 - PST which the correct time in GMT+1
But is wrong due to the wrong timezone info.
While on (Zope 2.7.6-final, python 2.3.5, linux2) the same code was showing : 28052005 03:56:07 - PDT This is not the correct time in GMT+1, but the current time on the server.
Now the timezone info is correct but the date does not use the correct timezone. Apparently, "strftime" is difficult...
What should have gone wrong and how do I solve this.
Search the mailing list archives for "strftime" problems... When I remember right, someone posted a patch fixing "strftime" problems. When I am wrong, file a bug report and (maybe) try to come up with working code. -- Dieter
participants (2)
-
Dieter Maurer -
Hamzat Kamal