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 implementation
> of DateTime and especially the timezone and daylight saving stuff.
> to be honest, it's completely hacked together :(

Yup.

> 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.

--
Lennart Regebro, Nuxeo     http://www.nuxeo.com/
CPS Content Management     http://www.cps-project.org/
_______________________________________________
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to