[ Lennart Regebro wrote:]
> On 11/21/05, Jürgen Herrmann <[EMAIL PROTECTED]> wrote:
>> recently i came up here with the intention to fix DateTime#strftime().
>> while trying this, i had to dig deeper and deeper into the
>> of DateTime and especially the timezone and daylight saving stuff.
>> to be honest, it's completely hacked together :(
>> sorry guys, i won't be able to completely fix this for now. i found
>> a way to monkey patch zope to make it work for my case (2 timezones
>> only). my plan is to completely reimplement DateTime, based on
>> python's datetime in my own freetime (maybe around xmas this year)
>> and give it back to the community.
> Well, that would be cool. Just a question: How do you plan to keep and
> verify backwards compatibility? Any database, with any type of
> DateTime object, must work transparently.
100% compatibility isn't desireable, because its broken atm ;P
>> XLhost.de - eXperts in Linux hosting <<
Bruderwöhrdstraße 15b, DE-93051 Regensburg
Fon: +49 (0)700 XLHOSTDE [0700 95467833]
Fax: +49 (0)721 151 463027
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -