[zope2-tracker] [Bug 142148] Re: DateTime default timezone wrong in some locations

Dylan Jay 142148 at bugs.launchpad.net
Tue Nov 9 23:15:12 EST 2010

Chris your fix is no better than the previous ones. It will break
american EST. This is a really hard problem to solve for all the reasons

The best work around for now is the one I mention in https://bugs.launchpad.net/zope2/+bug/501805.
We use this for all our australian clients. We're an Australian Plone integrator.

That is override the TZ env var on an instance by instance basis. (the
code below is up to date with the latest NSW timezone rules btw).

recipe = plone.recipe.zope2instance
environment-vars =
    TZ AEST-10AEDT-11,M10.1.0/02:00:00,M4.1.0/03:00:00

The only caveat is that there seems to be a bug in zope that to make
this work you have to run

bin/instance console

instead of runzope.py.

but I'm told "instance console" is now the recommended of running plone
in production anyway so it's not that much of an issue.

It would sitll be nice to have a zope (and python) that "just works" for

DateTime default timezone wrong in some locations
You received this bug notification because you are a member of Zope 2
Developers, which is the registrant for DateTime.

More information about the zope2-tracker mailing list