There is also a tedious, but workable solution for Python APIs that need to use DateTime both in and out of Zope; use hasattr(myDateTimeObject, 'tuple') to determine if the date time object you are using has a method called tuple(), which can be used to determine if you are using mxDateTime instead of Zope's... And you write code to support both modules... I had to do this with some library modules I am using in a project for relational data access in both Python-based automation utilities and Zope; this approach seems to work ok... Of course, this makes you subject to the limitations of Zope's DateTime, but I think that other than API incompatibility, that isn't as bad as it seems. Sean -----Original Message----- From: Stephan Richter [mailto:srichter@cbu.edu] Sent: Wednesday, December 05, 2001 7:53 AM To: Andreas Jung; Thomas B. Passin; zope@zope.org Subject: Re: [Zope] Manipulating Dates in Zope At 10:49 AM 12/5/2001 -0500, Andreas Jung wrote:

Sure, there is already a proposal in the Fishbowl to get rid of DateTime and replace it by mxDateTime. This will properly go into Zope 3.

AND THE WORLD REJOICED! FINALLY! :-) Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management _______________________________________________ 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 )