On 11.01.10 01:47, Martin Aspeli wrote:
> Laurence Rowe wrote:
>> I believe the current behaviour is intentional to preserve backwards
>> compatibility. See the discussion starting here:
>> Maybe it was 'fixed' on 2.10 branch some time later.
> Sorry, just to be clear - which behaviour is correct? The 2.10 one or
> the 2.12 one?
imho, the one from 2.10. i think about anyone would expect to have a
simple date given being interpreted as from their current time zone, no?
also, look at the following (using `DateTime` 2.12):
>>> from DateTime import DateTime
>>> now = DateTime()
>>> now == DateTime(now)
>>> now == DateTime(now.ISO())
this is a _pretty_ behaviour, to say the least! :)
> My vote would go for the 2.10 one - in the absence of timezone
> information, assume local timezone, not GMT.
> If we agree on that, is it clear what needs to be changed for this to work?
yes, i believe it is. we need to revert Laurence' revert
(http://zope3.pov.lt/trac/changeset/81213) and fix those BBB issues in
> Can we also agree that it's very bad for 2.10 and 2.12 to exhibit
> different behaviour here?
zeidler it consulting - http://zitc.de/ - i...@zitc.de
friedelstraße 31 - 12047 berlin - telefon +49 30 25563779
pgp key at http://zitc.de/pgp - http://wwwkeys.de.pgp.net/
plone 4.0 alpha released! -- http://plone.org/products/plone/
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -