UnknownTimezoneError / pytz quirks

erral · May 23, 2017, 6:01am

Be aware that GMT+N is not Etc/GMT+N but Etc/GMT-N.

I found this when migrating an old Plone from 3 to 5 and running some transmogrifier pipelines to create the new content.

Have a look here for more information: https://stackoverflow.com/questions/4008960/pytz-and-etc-gmt-5

If you are using transmogrifier, look to this blueprint to fix your datetime values:

gist.github.com

https://gist.github.com/gyst/c3739160a18cf52c93e0132da511b2ee

pytzfixer.py

# coding=utf-8
from zope.interface import classProvides, implements
from collective.transmogrifier.interfaces import ISectionBlueprint
from collective.transmogrifier.interfaces import ISection
from collective.transmogrifier.utils import Matcher, Condition

import logging
logger = logging.getLogger(__name__)

This file has been truncated. show original

pytzfixer.rst

Pytz timezone fixer section
===========================

This fixes the dreadful ``UnknownTimeZoneError: (UnknownTimeZoneError('GMT+1',)``
thrown by ``transmogrify.dexterity.schemaupdater`` when writing Event dates.
It turns out pytz does not recognize a timezone like ``GMT+1``.
This should be ``Etc/GMT+1``. This blueprint fixes that::

  [pytzfixer]
  blueprint = quaive.transmogrifier.sections.pytz.fixer

This file has been truncated. show original