Comment 21 for bug 142148

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 above.

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).

[instance]
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 AEST :)