Not quite non-US only, I had the same problem and I'm the Chicago-land area. I think part of the problem (if not all of it) is that Zope recognizes timezones as named in Unixen-land (hmm, sure am in a -land mood this morning), and has a little "difficulty" when it comes to recognizing what Windows considers to be proper timezone names (those guys never did figure out how to place nice with others). You can fix it locally by going in and editing DateTime.py, though of course you will have to reapply your changes the next time you upgrade. You just need to figure out what your system is calling the timezone you are in and adding an appropriate entry to the _zmap dictionary. Something like: 'Central Time':'GMT-6' Which, BTW, is what I had to do to get things working for my system. HTH, John
-----Original Message----- From: Graham Chiu [SMTP:anon_emouse@hotmail.com] Sent: Sunday, July 25, 1999 8:30 PM To: zope@zope.org Subject: Re: [Zope] Zope 2 ODBC date errors
In article <D133051DBC4AD111B90800A0C969498391D592@natasha.auslabs.lucen t.com>, Jay, Dylan <djay@lucent.com> writes
Its that damm timezone problem in zope. If the python string returned as your timezone is not known to zope it barfs. This problem has been going on for months and I feel because it is something that only effects non-american zope users there has not been enough effort into fixing it. In fact I have fixed this bug and submitted it and am disappointed that it has not made into the source yet as was promised. This is a show stopping bug. In certain countries any application that uses dates from sql where a timezone is not supplied is going to crash!!!
Is this something I can fix locally, or do I have to wait for the next beta?
------- Regards, Graham Chiu gchiu<at>compkarori.co.nz
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce
For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
In article <09A078107652D211A83700805F575E0519C7AC@dplmail6.internal.uop .com>, Miller, John M. <jmiller1@uop.com> writes
You can fix it locally by going in and editing DateTime.py, though of course you will have to reapply your changes the next time you upgrade. You just need to figure out what your system is calling the timezone you are in and adding an appropriate entry to the _zmap dictionary. Something like:
'Central Time':'GMT-6'
Thanks. I recalled that when I installed 1.11pr1 I had to do this, and tried this out first off yesterday. No go. Today, I replaced the _zmap with the contents of my 1.11pr1 _zmap, and that works now. ------- Regards, Graham Chiu gchiu<at>compkarori.co.nz
participants (2)
-
Graham Chiu -
Miller, John M.