If I have a vote, +1 on deprecation and replacement with something less
buggy. We have spent enormous amounts of time trying to sort out and then
work around DateTime problems. On the other hand, we have a substantial
amount of code that uses DateTime and finally, mostlyt works. We'd be
unhappy if we had to rewrite everything--so a long deprecation period
Timezones, BTW are just the tip of the iceberg. Datetime tries to be
a "it just works" solution to an inherently ambiguous problem and
incorporates many surprises.
On Fri, 25 Nov 2005, Chris Withers wrote:
> Peter Bengtsson wrote:
> > -1 on making DateTime deprecated. I'm sure thousands of zope people
> > use DateTime in thousands of places. Technically it might be correct
> > deprecate it but politically it's just going to put people off from
> > upgrading.
> I'm sure it would be fairly trivial to write an unpgrader, but really,
> deprecating it, even if the deprecation period is fairly long, is the
> only sane way to tackle this...
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -