[Zope-Coders] test failures in DateTime

Stephan Richter srichter@cbu.edu
Thu, 27 Sep 2001 21:19:15 -0500


At 08:52 PM 9/27/2001 -0400, Andreas Jung wrote:
>It seems nobody wants to own DateTime :-)
>I tried to solve these problems some time ago but I could not find
>the bug. FYI I wrote a fishboal proposal some time ago together with
>Stephan Richter with the goal to replace Zope DateTime module with
>mxDateTime.

I agree with Andreas (well, I should, shouldn;t I? :-) )! We should make an 
effort to move to mxDateTime. The advantages are very obvious and there is 
really no good reason not to do it. In fact, in a couple of days I would 
have had proposed that in anyway on this list. ;-)

Andreas and I (him more than me)  wrote already a module and tested it. 
Andreas do you still have the results? Using a certain configuration we had 
a performance increase of 6-10% I believe. After we were done there were 
only minor issues of places where an mxDateTime module would not work right 
away. I think the Catalog was one of them. But I think we could fix that 
fairly quickly.

The DateTime module is also very buggy. I have a lot of my users (of 
proiektor) from the West Coast writing me about DateTime problems and I had 
to patch the DateTime.py module. Also, mxDateTime is around for a long time 
and is pretty stable and really we would have another person on the team, 
since Marc maintains the product...

What do you guys think about that?

Regards,
Stephan

--
Stephan Richter
CBU - Physics and Chemistry Student
Web2k - Web Design/Development & Technical Project Management