I think I'd agree that mxDateTime is the problem. One way to approach this is to have an external method or utility module that imports mxDateTime and creates a bunch of proxy functions to the various mxDateTime constructors, like: import time #REQUIRES MX DATETIME!!!! from mx.DateTime import mktime def getMXDateTimeObject(timeTuple): """Given a time Tuple, Get MX DateTime object for date-calc and such""" obj = mktime(timeTuple) return obj This accomplishes getting mx DateTime objects without module namespace collision/confusion between the DateTime module in the mx package and the DateTime module in zope. -----Original Message----- From: Jens Vagelpohl [mailto:jens@zope.com] Sent: Tuesday, August 27, 2002 4:48 AM To: Ulrich Wisser Cc: zope@zope.org Subject: Re: [Zope] mxDateTime unauthorized remove mxDateTime? jens On Tuesday, Aug 27, 2002, at 07:06 US/Eastern, Ulrich Wisser wrote:
Hello,
I installed mxDateTime to my Zope 2.5.1. Unfortunatley can I no longer use DateTime. All methods are unauthorized. It seems that mxDateTime has replaced the "normal" DateTime module.
Any ideas how to fix this?
Thanks
Ulrich
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )